[jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-805) Extend BaseSessionContext.getRollbackOnly to cover transactions which have been asynchronously rolled back

Tue Dec 12 05:54:38 EST 2006

     [ http://jira.jboss.com/jira/browse/EJBTHREE-805?page=all ]

Dimitris Andreadis closed EJBTHREE-805.
---------------------------------------

    Resolution: Done

Committed the change to jbossAS branches 4.0, 4.2, trunk:
ejb/src/main/org/jboss/ejb3BaseSessionContext.java

> Extend BaseSessionContext.getRollbackOnly to cover transactions which have been asynchronously rolled back
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-805
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-805
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Kevin Conner
>         Assigned To: Dimitris Andreadis
>             Fix For: EJB 3.0 RC10 - FD
>
>
> The current implementation of BaseSessionContext.getRollbackOnly will return true if the current transaction context has status Status.STATUS_MARKED_ROLLBACK.
> If using JBossTS, a transaction timeout results in the transaction being rolled back asynchronously (not just marked for rollback).  Code using the getRollbackOnly method as an indicator of the current transaction status will not function as expected.
> The transaction status undergoes the following transition 
>   Status.STATUS_ACTIVE -> Status.STATUS_ROLLING_BACK -> Status.STATUS_ROLLEDBACK.
> Extending getRollbackOnly to check for Status.STATUS_MARKED_ROLLBACK, Status.STATUS_ROLLING_BACK and Status.STATUS_ROLLEDBACK will allow this code to function as expected.

-- 
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