-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
If there are two resources in a BasicAction there is an optimization that will cause the second resource to commit during prepare if the first resource returns XARD_ONLY.
This can cause data inconsistency in a transaction comprising of subordinates where the phase 2 decision is rollback.
- is caused by
-
JBTM-1511 Dynamic 1PC optimisation
- Closed
- is cloned by
-
JBEAP-12129 Disable dynamic1PC for subordinate transactions
- Closed
- is related to
-
JBTM-3020 Add ability for resources to indicate XA_RDONLY on end
- Open