[jbossts-issues] [JBoss JIRA] Updated: (JBTM-362) add failure does not cause rollback/end

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Wed May 21 05:30:02 EDT 2008

     [ http://jira.jboss.com/jira/browse/JBTM-362?page=all ]

Jonathan Halliday updated JBTM-362:

    Affects Version/s: 4.2.3.CP01

> add failure does not cause rollback/end
> ---------------------------------------
>                 Key: JBTM-362
>                 URL: http://jira.jboss.com/jira/browse/JBTM-362
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JTA Implementation, JTS Implementation
>    Affects Versions: 4.2.3.SP7, 4.3.0.GA, 4.2.3.CP01
>            Reporter: Mark Little
>         Assigned To: Jonathan Halliday
>             Fix For: 4.2.3.SP8, 4.4.CR1, 4.2.3.CP02
> BasicAction.add always assumes that a failure to add means the parameter (the participant) is tidied up by the caller if necessary. enlistResource doesn't do that, when it should: start has been called on the participant by the time BasicAction.add is called, which means that a failure at this stage needs end to be called. The transaction is going to be rolled back anyway, so nothing else needs to be done.

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


More information about the jbossts-issues mailing list