Hi, It is a relevant point. TransactionManager TM is seeing only OpenJPA Broker as participating resource in TM's global/JTA transaction GT. TxMgr is not seeing the transactions that is executing these queries on the slices for that matter. If the individual slices are to be brought under a JTA transaction (which becomes a branch of GT) then the broker effectively becomes the transaction manager.
A relevant question then is: is Broker XA-capable? The short answer is, currently, no. If a slice fails -- all bets are off and ACID is violated. But the published version of Slice is a rollback from a earlier, unit-tested (Fernando might vehemently shake his head or roll his eyes) implementation where Broker did employ a configurable, 2-phase capable TxMgr as and when it detected that each individual JDBC drivers for the slices are XA-capable. That XA part was not published on the principle of 'cross the bridge when it comes'. -- View this message in context: http://n2.nabble.com/slices-hangs-if-run-with-Multithreaded%3Dtrue-tp1645757p1649806.html Sent from the OpenJPA Developers mailing list archive at Nabble.com.
