Tightly/loosely coupled XA branches |
How does the AtomikosDataSourceBean go about implementing/differentiating tightly versus loosely coupled XA branches?
t.warren
Monday, August 29, 2011
Hi,
Two getConnection() requests will:
-use the same Xid (within the same tx and thread) if there is a close in between
-use different Xids if open concurrently
HTH
Guy Pardon
Monday, August 29, 2011
Thanks for the prompt answer.
t.warren
Monday, August 29, 2011
A related followup - when using the OracleXAResource interface, there is a flag, ORATRANSLOOSE, that I need to set. The OracleXAResouce start() method accepts the flag as an argument.
As this (the resource as well as all start methods) is hidden in AtomikosDataSourceBean, what route can be taken instead to specify this?
t.warren
Monday, August 29, 2011
I would also be interested to know if there is a way to get two concurrently open transactions with the same Xid (tightly coupled).
t.warren
Monday, August 29, 2011
Hi,
We've never had a request to:
1. set vendor-specific flags on the XAResource, or 2. tightly coupled Xids for concurrent connections
so no, this is not currently possible. Do you have any suggestions on how to achieve this?
Guy Pardon
Monday, September 05, 2011
|