[JBoss JIRA] Created: (JBAS-3938) CLONE -Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back
4:41 a.m.
CLONE -Extend EJBContext.getRollbackOnly to cover transactions which have been
asynchronously rolled back
---------------------------------------------------------------------------------------------------------
Key: JBAS-3938
URL: http://jira.jboss.com/jira/browse/JBAS-3938
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.5.GA
Reporter: Kevin Conner
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.0.CR1
The current implementation of EJBContext.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
4:41 a.m.
New subject: [JBoss JIRA] Moved: (EJBTHREE-805) CLONE -Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back
[ http://jira.jboss.com/jira/browse/EJBTHREE-805?page=all ]
Dimitris Andreadis moved JBAS-3938 to EJBTHREE-805:
---------------------------------------------------
Project: EJB 3.0 (was: JBoss Application Server)
Key: EJBTHREE-805 (was: JBAS-3938)
Issue Type: Task (was: Feature Request)
Fix Version/s: EJB 3.0 RC10 - FD
(was: JBossAS-4.2.0.CR1)
Affects Version/s: EJB 3.0 RC9 - FD
(was: JBossAS-4.0.5.GA)
CLONE -Extend EJBContext.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 EJBContext.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
4:49 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-805) Extend BaseSessionContext.getRollbackOnly to cover transactions which have been asynchronously rolled back
[ http://jira.jboss.com/jira/browse/EJBTHREE-805?page=all ]
Dimitris Andreadis updated EJBTHREE-805:
----------------------------------------
Summary: Extend BaseSessionContext.getRollbackOnly to cover transactions which
have been asynchronously rolled back (was: CLONE -Extend EJBContext.getRollbackOnly to
cover transactions which have been asynchronously rolled back)
Description:
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.
was:
The current implementation of EJBContext.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.
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
4:54 a.m.
New subject: [JBoss JIRA] Closed: (EJBTHREE-805) Extend BaseSessionContext.getRollbackOnly to cover transactions which have been asynchronously rolled back
[ 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
6546
days inactive
6546
days old
3 comments
1 participants
participants (1)
-
Dimitris Andreadis (JIRA)