-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR4
-
None
There exists a defect that if a recovering JVM does the following steps:
doRecoveryScan() waitForOrphanInterval() doRecoveryScan()
Before XATerminator::recover is called in the root coordinator then bottom-up recovery will be told there is NoTransaction which is infers as a rollback.
I saw two options, one was to have TransactionCacheItem try to peek in the objectstore for ServerTransaction/JCA classes. The alternative is to add a new recovery module that can load the ServerTransaction/JCA classes periodically so the transaction won't be lost.
- clones
-
JBTM-2748 Prevent JTS bottom-up recovery from rolling back prepared inflowed JCA transactions
- Closed
- is incorporated by
-
WFLY-7241 Upgrade Narayana to 5.3.5.Final
- Closed
- is related to
-
JBEAP-7355 JTS bottom-up could roll-back prepared inflowed JCA transactions
- Closed
-
JBTM-2791 JTS bottom-up could roll-back prepared inflowed JCA transactions
- Closed
- relates to
-
JBEAP-11154 JCA inflow transaction committed by recovery is not removed from tx log when JTS is used
- Closed