While testing tx recovery in OpenShift I see that recovery doesn't completely finish in some tests.
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
ejb server XA resource 2 crashes JVM in commit method phase. (the same outcome client crashes at commit phase)
Test waits until crashed pod is restarted, then forces periodic recovery twice and then checks that transaction log store is empty. But it is not empty, however it looks like all XA resources were commited.
Attached are logs from client and server pods.
- is blocked by
-
WFCORE-4659 Partial revert of *not* having static default authentication context
- Closed
- is caused by
-
WFTC-75 XA file registry does not delete records when network failure happens during commit
- Resolved
- is related to
-
WFWIP-203 Transaction recovery may hit a wrong server when remote side works with multiple pods
- Resolved
-
WFLY-12453 Update wildfly-transaction-client to 1.1.7.Final
- Closed