[ https://issues.jboss.org/browse/WFWIP-218?page=com.atlassian.jira.plugin.... ] Martin Simka updated WFWIP-218: ------------------------------- Description: 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 * Scenario 1 - 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 aren't commited * Scenario 1 - testTxStatelessServerSecondCommitThrowRmFail* {noformat} /opt/eap/standalone/data/ejb-xa-recovery/20005_00000000000000000000ffffac11000aa3c95b225d932d5e0000001374782d636c69656e742d30_00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 {noformat} was: 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 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 {noformat} /opt/eap/standalone/data/ejb-xa-recovery/20005_00000000000000000000ffffac11000aa3c95b225d932d5e0000001374782d636c69656e742d30_00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)