[jbossts-issues] [JBoss JIRA] (JBTM-3034) CMR recovery wrongly handles commit and rollback

[Ondra Chaloupka (JIRA)]

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

Ondra Chaloupka commented on JBTM-3034:
---------------------------------------

After more investigation I found the observed issues is the same in all cases. The CMR which is committed then causes the resource is called to be rolled-back too. The regression seems to be caused by the fact that the {{XAResource}} is withdrawn from the {{XAResourceRecord}} https://github.com/jbosstm/narayana/blob/5.8.2.Final/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/resources/arjunacore/XAResourceRecord.java#L1254 during recovery (in second phase by {{AtomicActionRecoveryModule}}) and the {{_xidScans}} is not updated with that fact (https://github.com/jbosstm/narayana/blob/5.8.2.Final/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L289).
This was done intentionally for {{XATerminator}} recovery does not add warnings {{noxaresource}} (https://github.com/jbosstm/narayana/pull/1059/files#diff-8487f43e773b3321c5396187b559bfffL261) but it seems not correct from CMR point of view.

> CMR recovery wrongly handles commit and rollback 
> -------------------------------------------------
>
>                 Key: JBTM-3034
>                 URL: https://issues.jboss.org/browse/JBTM-3034
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>    Affects Versions: 5.8.1.Final
>            Reporter: Ondra Chaloupka
>            Assignee: Ondra Chaloupka
>
> The recovery of CMR works wrongly.
> For scenario I currently investigate there is issue the second resource beging committed and rolled-back too.
> # cmr resource prepare (no real action on the local transction)
> # xa resource prepare (prepared in real as XA)
> # cmr resource commit (commiting the local transaction)
> # JVM crash
> # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue.
> This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed.
> This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)