[jboss-jira] [JBoss JIRA] (WFLY-12922) server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited

Ondrej Chaloupka (Jira) issues at jboss.org
Fri Jan 3 09:49:59 EST 2020


     [ https://issues.redhat.com/browse/WFLY-12922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondrej Chaloupka moved WFWIP-218 to WFLY-12922:
-----------------------------------------------

        Project: WildFly  (was: WildFly WIP)
            Key: WFLY-12922  (was: WFWIP-218)
    Component/s: EJB
                 Transactions
                     (was: OpenShift)


> server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited
> --------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-12922
>                 URL: https://issues.redhat.com/browse/WFLY-12922
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Transactions
>            Reporter: Martin Simka
>            Assignee: Ondrej Chaloupka
>            Priority: Major
>
> 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.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jboss-jira mailing list