Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.2, 3.0.0
-
Security Level: public (Regular issues)
-
None
Description
The following sequence of events can result in a tx branch stuck in a RM until geronimo is restarted and recovers transactions:
1. tx branch prepares
2. geronimo decides to rollback the tx
3. RM crashes
4. attempt to rollback branch fails with e.g. a RETRY error code.
We can do the same as we do for commits with rollbacks and keep trying until we succeed. I think we can also unify the two rollbackResources methods.