[jbossts-issues] [JBoss JIRA] (JBTM-3138) XTS txbridge does not run commit when succesfully prepared on crash recovery

[Ondrej Chaloupka (Jira)]

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

Ondrej Chaloupka commented on JBTM-3138:
----------------------------------------

It seems the recovery calls {{commit}} but the {{coordinator}} on the {{Prepared}} command is {{null}} (https://github.com/jbosstm/narayana/blob/5.9.5.Final/XTS/WS-T/dev/src/com/arjuna/wst11/messaging/CoordinatorProcessorImpl.java#L135). Because of that the rollback is sent (https://github.com/jbosstm/narayana/blob/5.9.5.Final/XTS/WS-T/dev/src/com/arjuna/wst11/messaging/CoordinatorProcessorImpl.java#L150).

It sounds that the {{Coordinator}} instance is not activated for the durable participant (e.g. named as {{D0:ffff0a280527:4bf12fc8:5cbf1cd7:1d}}). The reason is under investigation.

> XTS txbridge does not run commit when succesfully prepared on crash recovery
> ----------------------------------------------------------------------------
>
>                 Key: JBTM-3138
>                 URL: https://issues.jboss.org/browse/JBTM-3138
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: XTS
>    Affects Versions: 5.9.5.Final
>            Reporter: Ondrej Chaloupka
>            Assignee: Ondrej Chaloupka
>            Priority: Critical
>
> As it seems the crashed inbound txbridge participant finished with rollback after recovery is run on the prepared participant.
> In scenario
> * WS call to the WFLY server
> * inbound bridge injects the JTA transactions as subordinate under the WS AT one
> * prepare is called and the 2PC phase finishes
> * commit phase starts and JVM crashes
> * restart of WFLY server
> * recovery is expected to commit the participants
> the outcome is rollback for the participant not the commit as it's expected. This way the data consistency could be harmed.
> This was discussed at the forum https://developer.jboss.org/thread/279243 as follow-up to the issue JBTM-3079.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)