Can you determine if this occurs when a second connection is requested within one transaction? Any more information you can supply on the context in which this occurs would be helpful.
This happens systematically at the first time a connection is asked in the first transaction started. Then it still happens quite often, but it is not systematic and seems not to be reproductible (I cannot determine a sequence of operations in my application that will induce the problem for sure).
So, this is the first connection within the transaction.However, other connections in a non-transcational context have already succesfully been provided and closed.
Note that the transaction is bean-managed. The UserTransaction is retrieved through a JNDI lookup and not through the ejb context. This was done only for design reasons. If you think that this can be the cause of the problem, I'll do some refactoring to be able to change this, but from what I understand of JTA and EJB's, this should be strictly equivalent???
I have quickly made some changes to the code in order to retrieve the transaction from the SessionContext of my Session Bean instead of a JNDI lookup. I confirm that this does not change anything...
Thanks for your help,
Still can't find any solution...
Has someone already successfully used IBM DB2 with distributed transactions and JBoss 3?
have you found a solution for your problem ?
I'm using jboss 3.0.4 with db2 7.2 xa driver and the same error occurs ..
The xa support in 3.0 has not been satisfactory until now. I recommend trying with current cvs version or 3.2RC2. Make sure the TrackConnectionByTx flag is set to true: I think this will remove the circumstances in which this error occurred.