Friday, June 21, 2002 05:52 PM
This has been resolved. There was a bug in the JBoss XA TM, which was using TMSUCCESS instead of TMSUSPEND on delist().
This would have only been a problem if durring the same TX, after the client code had a reference to the connection, one or more EJB's were called (with Required at least, but I did not test other tx modes). When the EJB's method returned the connection was delisted (due to some over active delisting/enlisting inside of the JBoss3 container) and its state was set incorrectly, thus when it attempted to relist it thought it should TMJOIN instead of TMRESUME.
If no EJB's were called between the connection creation, connection close and tx commit then this bug would have never shown up.
This has been fixed in the latest CVS for HEAD and Branch_3_0.
Thanks for your patience. Your help allowed me (one who knows nothing about XA) to get this resolved.