[
http://jira.jboss.com/jira/browse/JBTM-278?page=comments#action_12372503 ]
Mark Little commented on JBTM-278:
----------------------------------
Any fix should be within the XAResourceRecord code and not the coordinator. That's
because in general with 1PC, the outcome of the transaction is dictated by the single
participant and not the coordinator. We try to optimise away the amount of intentions list
processing we do, so that's why we don't call rollback on the participant. We
should continue to do that in the coordinator (BasicAction), which is participant
agnostic, and stick this fix in the prepare code for the XAResourceRecord.
XAResource.end error may not cause rollback
-------------------------------------------
Key: JBTM-278
URL:
http://jira.jboss.com/jira/browse/JBTM-278
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.2.3.SP5
Reporter: Jonathan Halliday
Assigned To: Mark Little
Fix For: 4.4
An XAResource.end call may return an XA_RB* error. In such case, the resource should (but
currently does not) still get rollback called on it too. Update XAResourceRecord.java to
fix.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira