You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by de...@geronimo.apache.org on 2004/10/04 21:13:38 UTC
[jira] Created: (GERONIMO-355) tx policies call tm.rollback on committed transactions
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-355
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-355
Summary: tx policies call tm.rollback on committed transactions
Type: Bug
Status: Unassigned
Priority: Major
Project: Apache Geronimo
Components:
OpenEJB
Versions:
1.0-M2
Assignee:
Reporter: David Jencks
Created: Mon, 4 Oct 2004 12:13 PM
Updated: Mon, 4 Oct 2004 12:13 PM
Description:
The tx policies generally try to rollback on any Throwable. If the tx was marked RollbackOnly, the previous commit will have ended the tx by rolling back and removed the tx-thread association. Rolling back by calling tm.rollback will result in problems due to the missing tx-thread association.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-355) tx policies call tm.rollback on committed transactions
Posted by de...@geronimo.apache.org.
The following comment has been added to this issue:
Author: David Jencks
Created: Tue, 5 Oct 2004 12:15 AM
Body:
This is fixed for container policies. BMT policies require more thought. The CMT fix won't be completely correct until RollbackExceptions are translated into the proper TransactionRolledBack[Local]Exception (see GERONIMO-359).
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/GERONIMO-355?page=comments#action_53704
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-355
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-355
Summary: tx policies call tm.rollback on committed transactions
Type: Bug
Status: Open
Priority: Major
Project: Apache Geronimo
Components:
OpenEJB
Versions:
1.0-M2
Assignee: David Jencks
Reporter: David Jencks
Created: Mon, 4 Oct 2004 12:13 PM
Updated: Tue, 5 Oct 2004 12:15 AM
Description:
The tx policies generally try to rollback on any Throwable. If the tx was marked RollbackOnly, the previous commit will have ended the tx by rolling back and removed the tx-thread association. Rolling back by calling tm.rollback will result in problems due to the missing tx-thread association.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-355) tx policies call tm.rollback on committed transactions
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-355?page=history ]
David Jencks closed GERONIMO-355:
---------------------------------
Resolution: Fixed
Fix Version: 1.0-M4
Dain fixed this while working on transaction policies
> tx policies call tm.rollback on committed transactions
> ------------------------------------------------------
>
> Key: GERONIMO-355
> URL: http://issues.apache.org/jira/browse/GERONIMO-355
> Project: Geronimo
> Type: Bug
> Components: OpenEJB
> Versions: 1.0-M2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0-M4
>
> The tx policies generally try to rollback on any Throwable. If the tx was marked RollbackOnly, the previous commit will have ended the tx by rolling back and removed the tx-thread association. Rolling back by calling tm.rollback will result in problems due to the missing tx-thread association.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira