[jbossts-issues] [JBoss JIRA] (JBTM-1786) Change to TMFAIL for an ABORT on a non-prepared TX

RH Bugzilla Integration (JIRA) jira-events at lists.jboss.org
Wed Jul 24 09:40:26 EDT 2013

     [ https://issues.jboss.org/browse/JBTM-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

RH Bugzilla Integration updated JBTM-1786:

    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=978589, https://bugzilla.redhat.com/show_bug.cgi?id=986046, https://bugzilla.redhat.com/show_bug.cgi?id=987970  (was: https://bugzilla.redhat.com/show_bug.cgi?id=978589, https://bugzilla.redhat.com/show_bug.cgi?id=986046)

> Change to TMFAIL for an ABORT on a non-prepared TX
> --------------------------------------------------
>                 Key: JBTM-1786
>                 URL: https://issues.jboss.org/browse/JBTM-1786
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JTA, JTS
>    Affects Versions: 4.16.4
>            Reporter: Johnathon Lee
>            Assignee: Johnathon Lee
>             Fix For: 4.17.7, 5.0.0.M4
> An ABORT on a non-prepared TX should be calling end with TMFAIL.
> It's more efficient in that the RM can return an RB* code immediately and short circuit the rollback internally if it likes.  More importantly though the RM is less likely to object that it's still running tx activity on another thread and the concurrent TMSUCCESS therefore makes no sense to it.
> Also the XAResourceRecord.topLevelAbort code should immediately continue on to calling rollback on the resource despite the failed end(). 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the jbossts-issues mailing list