-
Bug
-
Resolution: Done
-
Major
-
1.1.2.Final
-
None
ejb-xa-recovery logs were introduced in WFTC-38/WFLY-10201. in order to enable correct recovery of transactions in which client were interrupted in the prepare phase.
Those logs are not being cleared after the attempted recovery.
Example scenario:
1. transaction starts on A
2. A->B invocation is performed
3. B is enlisted as a subordinate resource
4. A's host crashes during prepare phase (ejb-xa-recovery record created on A, no records created on B).
5. A is restarted and performs recovery.
6. A asks B about XA resources associated with the transaction
7. B returns empty lists
8. A finishes recovery cycle
In the scenario above ejb-xa-recovery logs are not being cleared leading to infinite recovery loop for them.
- is related to
-
WFLY-12090 Unknown service name jboss.ejb and txn
- Closed
- relates to
-
WFTC-38 Add active outflowed transaction persistence to JBoss (Narayana) provider
- Resolved