-
Bug
-
Resolution: Done
-
Major
-
7.1.0.GA
-
None
-
Regression
-
-
-
-
-
-
-
The transaction manager contains a but as a regression in CMR behavior against EAP 7.0.0. If periodic recovery should commit the transaction as the correct outcome of after the crash (or network failure) the XA resource is not only committed but immediately the rollback is called in addition.
This seems do not cause a data consistency issue. But it could make XA resource blaming with errors or in wrong state (depends on the XA resource implementation).
- clones
-
JBTM-3061 CMR recovery wrongly handles commit and rollback
- Closed
- is caused by
-
JBTM-3034 CMR recovery wrongly handles commit and rollback
- Closed
- is incorporated by
-
JBEAP-15891 [GSS](7.1.z) Upgrade Narayana from 5.5.32 to 5.5.33
- Closed
-
JBEAP-16015 [GSS](7.1.z) Upgrade Narayana from 5.5.32 to 5.5.34
- Closed