[
https://issues.jboss.org/browse/JBTM-3034?page=com.atlassian.jira.plugin....
]
Ondra Chaloupka commented on JBTM-3034:
---------------------------------------
Based on the discussion on the forum
[
https://developer.jboss.org/message/983892|https://developer.jboss.org/me...]
there should not be the issue of {{XATerminator}} which would not be capable to commit the
inflow transaction. By reverting back the change introduced by JBTM-2734 at
XARecoveryModule#getNewXAResource
https://github.com/jbosstm/narayana/pull/1059/files#diff-8487f43e773b3321...
we should not cause any functionality error (possible a warning log message
nonxaresourcerecovery could be shown in some tooling corner cases).
I have tried to use different approach, than the reverting one which will be published in
PR, which is checking in XARecoveryModule if CMRRecoveryModule knows about the XAResource.
It's presented in branch
https://github.com/ochaloup/narayana/tree/JBTM-3034-cmr-failures and the changeset is
uploaded here in diff at
https://issues.jboss.org/secure/attachment/12437356/JBTM-3034-xarm-to-que...
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
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.5.0#75005)