Community

HornetQ RA integration

reply from Tim Fox in JCA - View the full discussion

To clarify, this is the problem we have.

 

AS gets a managed connection and calls getLocalTransaction(), this results internally in the RA creating a transacted local session.

 

The user does work with that connection, then finished, it gets returned to the pool.

 

Next user wants an XA connection, AS gets the same cached managed connection, getXAResource is called, but the resource is never enlisted in a tx.

 

This causes us to use the local  transacted session we cached earlier on the connection, but it's transacted, and the behaviour we require is an XA session behaves as non transacted non XA session when not enlisted.

Reply to this message by going to Community

Start a new discussion in JCA at Community