[jbossts-issues] [JBoss JIRA] (JBTM-3034) CMR recovery wrongly handles commit and rollback
Tom Jenkinson (Jira)
issues at jboss.org
Thu Dec 6 12:38:00 EST 2018
[ https://issues.jboss.org/browse/JBTM-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Jenkinson updated JBTM-3034:
--------------------------------
Fix Version/s: 5.5.33.Final
> 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
> Priority: Major
> Fix For: 5.5.33.Final, 5.9.0.Final
>
> Attachments: JBTM-3034-xarm-to-query-cmrrm.diff
>
>
> 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.12.1#712002)
More information about the jbossts-issues
mailing list