This is a strange error, because the BAD_INV_ORDER with minor code 4 is usually thrown when code attempts to invoke a method after the ORB has shut down. This error usually describes operations being executed in the wrong order, like invoking methods on a stub before initializing the ORB, or after the ORB has shut down.
Is it easy to reproduce the errors you are seeing? If so, and if you provide me a testcase that is failing I can take a look at it later.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137776#4137776
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137776
"ALRubinger" wrote : I have committed org.jboss.jbossas:jboss-as-dependency:
|
| http://jira.jboss.com/jira/browse/JBAS-5324
|
| Looking to avoid being too invasive here. The shared POM is now committed and deployed for review, though I'm holding the commit for org.jboss.jbossas:jboss-as-parent until we can verify that all looks allright. Once Paul gives me the nod, I'll commit that change.
|
| The patch up for review is attached to the JIRA, as is the commit of the new project.
|
| Paul, let's look over this together.
|
| S,
| ALR
Hey Andrew, I think it's fine to commit this, except for the prerequisites section (maven 2.0.8). I think that should stay in the jbossas parent because it doesn't get inherited. If ejb also requires 2.0.8 you'll have to define it in that parent also.
Also, I must have committed the 2.2-beta-3-SNAPSHOT version of the assembly plugin by mistake. I was working with that locally, but the one in the pom should be 2.2-beta-2.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137771#4137771
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137771
Adrian and the JBossAS team:
I'm fixing http://jira.jboss.com/jira/browse/JBAS-5081 for use in JBossAS 4.2 and will then port across to 5.0
I'm trying to get my head around how to write JBossAS testsuite tests, specifically one that will cover this.
I don't see any way in the AS to get the object that implements TransactionTimeoutConfiguration in a pluggable fashion. The best I can do is assume that the TransactionManager also implements it and cast appropriately. Do we need a TransactionTimeoutConfigurationLocator to live alongside of the TransactionManagerLocator?
Also, what do I do in the case of a new test like this that I know is going to fail until the next JBossTS release is available for consumption by the AS? Check it in anyhow and accept that the testsuite won't pass for a few weeks?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137770#4137770
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137770
Adrian and the JBossAS team:
I'm fixing http://jira.jboss.com/jira/browse/JBAS-5081 for use in JBossAS 4.2 and will then port across to 5.0
I'm trying to get my head around how to write JBossAS testsuite tests, specifically one that will cover this.
I don't see any way in the AS to get the object that implements TransactionTimeoutConfiguration in a pluggable fashion. The best I can do is assume that the TransactionManager also implements it and cast appropriately. Do we need a TransactionTimeoutConfigurationLocator to live alongside of the TransactionManagerLocator?
Also, what do I do in the case of a new test like this that I know is going to fail until the next JBossTS release is available for consumption by the AS? Check it in anyhow and accept that the testsuite won't pass for a few weeks?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137769#4137769
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137769
"adrian(a)jboss.org" wrote :
| I'm going to remove this test.
|
Can you just comment it + a big TODO?
And I'll adjust it accordingly to the new behavior.
"adrian(a)jboss.org" wrote :
| The test actually suffers from a race anyway.
| The deployment threads (as written currently) could run after the shutdown thread gets the lock which means the test would fail.
The test is designed in such a way that threads that come after shutdown should fail.
But yeah, I need to look into that race anyway.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137764#4137764
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137764
Related to this:
http://jira.jboss.com/jira/browse/JBDEPLOY-19
There's some code/test I'm going break
relating to shutdown and single deployment.
It was DeployerSingleDeploymentTestCase::testMultiThreadsAndShutdown()
This is incorrect behaviour.
The shutdown should not be blocked by a deployment, it were
it could "deadlock" the shutdown when the deployment is misbehaving (e.g. a broken service
that is waiting on a socket forever because of a network split)
I'm going to remove this test.
The test actually suffers from a race anyway.
The deployment threads (as written currently) could run after the shutdown thread
gets the lock which means the test would fail.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137759#4137759
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137759