-
Bug
-
Resolution: Done
-
Major
-
18.0.0.Final
-
None
this follows up on WFWIP-206
While testing tx recovery in OpenShift I see that scale down of pod that has transaction in-doubt on it isn't successful
Scenario:
ejb client (app tx-client, pod tx-client-0):
- EJB business method
- lookup remote EJB
- enlist XA resource 1 to transaction
- enlist XA resource 2 to transaction
- call remote EJB
ejb server (app tx-server, pod tx-server-0):
- EJB business method
- enlist XA resource 1 to transaction
- enlist XA resource 2 to transaction
testTxStatelessServerSecondCommitThrowRmFail
ejb server XA resource 2 fails with XAException(XAException.XAER_RMFAIL)
Then the test calls scale down (size from 1 to 0) on tx-server pod. Server scale down completes but sometimes there some records left in <JBOSS_HOME>/standalone/data/ejb-xa-recovery on tx-client and transactions on client aren't commited.
- is caused by
-
WFTC-77 Provide correct integration of SubordinateXAResource with Narayana recovery
- Resolved
- is related to
-
JBEAP-19435 (7.3.z) WFTC registry records may not be removed during the OpenShift scale down processing when transaction recovery commits
- Closed
-
WFLY-12910 Upgrade wildfly-transaction-client to 1.1.9.Final
- Closed
- relates to
-
WFWIP-206 scale down isn't successful when there are in-doubt transaction on pod
- Resolved