Bug #868
Support enlist=JTA in Z2 Data Source
Added by Udo Offermann over 12 years ago.
Updated over 12 years ago.
Description
Currently the WorkUnit is the DS enlist container. This way there is always a TX.
Standard behavior would leave TX boundaries to JTA and hence there would be none by default and the use of UserTX or @Transactional defines TX boundaries.
- Assignee deleted (
Redmine Admin)
In other words: The issue here is that the Z2 implemented Data Source is not enlisting with JTA today.
This issue should be handled in conjunction with #877
- Assignee set to Henning Blohm
- Target version set to 3
- Target version changed from 3 to 2.1
- Status changed from New to Rejected
Rejected, as we do not want to go down the road of providing XA capable connection pooling over arbitrary TMs.
See also http://www.atomikos.com/Documentation/ExternalConnectionPool.
Z2-Env built-in connection pooling only works for single-tx case, at best integrated with the single-commit-phase JTA impl over the z2 work unit.
Also available in: Atom
PDF
Updated by