[jboss-jira] [JBoss JIRA] (WFWIP-201) incomplete tx recovery on openshift

Ondrej Chaloupka (Jira) issues at jboss.org
Mon Sep 16 08:15:01 EDT 2019


    [ https://issues.jboss.org/browse/WFWIP-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784652#comment-13784652 ] 

Ondrej Chaloupka commented on WFWIP-201:
----------------------------------------

The issue with the authentication was resolved by applying the fix of https://issues.jboss.org/browse/WFCORE-4659 (merged for WFCORE 10.0.0.Beta9) . Confirmed by testing and with [~simkam]. Resolving this issue.

> incomplete tx recovery on openshift
> -----------------------------------
>
>                 Key: WFWIP-201
>                 URL: https://issues.jboss.org/browse/WFWIP-201
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: OpenShift
>            Reporter: Martin Simka
>            Assignee: Ondrej Chaloupka
>            Priority: Blocker
>         Attachments: auth_fail.txt, tx-client-0.txt, tx-server-0.txt
>
>
> 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. 



--
This message was sent by Atlassian Jira
(v7.13.5#713005)


More information about the jboss-jira mailing list