Hi Clebert. I'll try to take a stab at this, but I think I need more information from
you.
"clebert.suconic(a)jboss.com" wrote : I need some help understanding this...
|
| XAResourceRecoveryTest::testRecoveryOnSend will aways fail if running after
XARecoveryTest::testMockCoordinatorRecoveryWithJBossTSXids.
|
Fails in what way? Can you c&p the precise error message you get?
anonymous wrote :
| After some investigation, XAResourceRecoveryTest would fail by simply initializing
TxControl by calling any method (such as TxControl.isEnabled()).
|
That should be OK. This class is just a wrapper/helper for things that are idempotent.
anonymous wrote :
|
http://anonsvn.jboss.org/repos/messaging/trunk/tests/src/org/jboss/test/m...
|
| This is because testMockCoordinatorRecoveryWithJBossTSXids is instantiating
com.arjuna.ats.jta.xa.XidImple, and that is initializing TxControl which is starting a
ObjectStore.
|
No, it doesn't start an objectstore (an objectstore can never be started). It assigns
one to the instance variable if one has not already been created, but that's it and it
should be idempotent, i.e., subsequent tests would just do the same thing if they had to
start from scratch.
anonymous wrote :
| Later on testRecoveryOnSend, the test would get a message "Told not to rollback
{0}" on logs. I still don't know what's the reason but any help is welcome.
|
This message is coming from recovery and is because the recovery module has found some
Xids that it doesn't know about and rather than roll it back (which would be bad if
the machine/objectstore is being shared between other TM instances) it puts out this
warning and ignores it. Check the TS failure docs on NodeName. If you can't find it,
ping me on IM.
anonymous wrote :
| I was considering to comment the Mock Test out until we find a way to use the XidImple
directly.
|
Hopefully that won't be necessary.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082030#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...