The whole point of xa rather than 2pc IMO is that a connection can be used in many transactions sequentially without the transaction being committed. A typical use of a connection/xaresource would be
get connection from pool (app)
enlist in current tx/xid (jboss)
do some work (app)
close handle (app)
delist from current tx/xid (jboss)
put back in pool (jboss).
At this point the connection should be available for use by another thread/tx/xid even though the first tx has not completed.
What jboss/db are you using?
> The whole point of xa rather than 2pc IMO is that a
> connection can be used in many transactions
> sequentially without the transaction being committed.
The Sybase XA engineers stated that this is not possible. The transaction must be committed before the connection can be released to _another_ transaction.
Looking more closely at the jBoss code, it looks like the XA connections listen to transaction events, and are supposed to be released to the pool when the transaction completes or fails. i am in the process of debugging this code now.
> A typical use of a connection/xaresource would be
> What jboss/db are you using?
jBoss 2.6/Sybase 12.5 - Can't go to jBoss 3.0 until the associateConnection is working for XA.