[JBoss JIRA] Created: (JBAS-3847) Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back
10:46 a.m.
Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously
rolled back
--------------------------------------------------------------------------------------------------
Key: JBAS-3847
URL: http://jira.jboss.com/jira/browse/JBAS-3847
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.5.GA
Reporter: Kevin Conner
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 was opened via salesforce https://na1.salesforce.com/50030000002X6dw.
--
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
10:56 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-3847) Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back
[ http://jira.jboss.com/jira/browse/JBAS-3847?page=all ]
Luc Texier updated JBAS-3847:
-----------------------------
Description:
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.
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.
This was opened via salesforce https://na1.salesforce.com/50030000002X6dw.
Extend EJBContext.getRollbackOnly to cover transactions which have
been asynchronously rolled back
--------------------------------------------------------------------------------------------------
Key: JBAS-3847
URL: http://jira.jboss.com/jira/browse/JBAS-3847
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: JBossAS-4.0.5.GA
Reporter: Kevin Conner
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
2:25 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-3847) Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back
[ http://jira.jboss.com/jira/browse/JBAS-3847?page=all ]
Luc Texier updated JBAS-3847:
-----------------------------
Fix Version/s: JBossAS-4.2.0.CR1
Extend EJBContext.getRollbackOnly to cover transactions which have
been asynchronously rolled back
--------------------------------------------------------------------------------------------------
Key: JBAS-3847
URL: http://jira.jboss.com/jira/browse/JBAS-3847
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: JBossAS-4.0.5.GA
Reporter: Kevin Conner
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
10:10 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-3847) Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back
[ http://jira.jboss.com/jira/browse/JBAS-3847?page=all ]
Dimitris Andreadis reassigned JBAS-3847:
----------------------------------------
Assignee: Dimitris Andreadis
Extend EJBContext.getRollbackOnly to cover transactions which have
been asynchronously rolled back
--------------------------------------------------------------------------------------------------
Key: JBAS-3847
URL: http://jira.jboss.com/jira/browse/JBAS-3847
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
12:27 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-3847) Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back
[ http://jira.jboss.com/jira/browse/JBAS-3847?page=all ]
Dimitris Andreadis closed JBAS-3847.
------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
JBossAS-4.0.5.SP1
Resolution: Done
Applied the change to all brances.
Extend EJBContext.getRollbackOnly to cover transactions which have
been asynchronously rolled back
--------------------------------------------------------------------------------------------------
Key: JBAS-3847
URL: http://jira.jboss.com/jira/browse/JBAS-3847
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-5.0.0.Beta2, JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1
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
6411
days inactive
6440
days old
4 comments
3 participants
participants (3)
-
Dimitris Andreadis (JIRA) -
Kevin Conner (JIRA)
-
Luc Texier (JIRA)