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/06/23 03:30:27 UTC
[jira] Created: (GERONIMO-250) Connector tries to commit after connection error
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-250
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-250
Summary: Connector tries to commit after connection error
Type: Bug
Status: Unassigned
Priority: Major
Project: Apache Geronimo
Components:
connector
Versions:
1.0-M2
Assignee:
Reporter: Simon Godik
Created: Tue, 22 Jun 2004 6:29 PM
Updated: Tue, 22 Jun 2004 6:29 PM
Description:
If a resource adapter indicates a connection has had a fatal error, then the connection manager destroys the managed connection but still attempts to commit/rollback at transaction end. This is bad as the connection has already been destroyed.
---------------------------------------------------------------------
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] Updated: (GERONIMO-250) Connector tries to commit after
connection error
Posted by "Prasad Kashyap (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasad Kashyap updated GERONIMO-250:
------------------------------------
Fix Version/s: (was: 2.0-M5)
Verification Required
> Connector tries to commit after connection error
> ------------------------------------------------
>
> Key: GERONIMO-250
> URL: https://issues.apache.org/jira/browse/GERONIMO-250
> Project: Geronimo
> Issue Type: Bug
> Components: connector
> Affects Versions: 1.0-M2
> Reporter: Simon Godik
> Assignee: David Jencks
> Fix For: Verification Required
>
>
> If a resource adapter indicates a connection has had a fatal error, then the connection manager destroys the managed connection but still attempts to commit/rollback at transaction end. This is bad as the connection has already been destroyed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-250) Connector tries to commit after
connection error
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-250?page=all ]
David Jencks updated GERONIMO-250:
----------------------------------
Fix Version/s: 2.0
(was: 1.x)
> Connector tries to commit after connection error
> ------------------------------------------------
>
> Key: GERONIMO-250
> URL: http://issues.apache.org/jira/browse/GERONIMO-250
> Project: Geronimo
> Issue Type: Bug
> Components: connector
> Affects Versions: 1.0-M2
> Reporter: Simon Godik
> Assigned To: David Jencks
> Fix For: 2.0
>
>
> If a resource adapter indicates a connection has had a fatal error, then the connection manager destroys the managed connection but still attempts to commit/rollback at transaction end. This is bad as the connection has already been destroyed.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-250) Connector tries to commit after connection error
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-250?page=all ]
Aaron Mulder updated GERONIMO-250:
----------------------------------
Fix Version: 1.0-M5
Environment:
Looks like a pretty old issue, but please see if it's still valid for M5.
> Connector tries to commit after connection error
> ------------------------------------------------
>
> Key: GERONIMO-250
> URL: http://issues.apache.org/jira/browse/GERONIMO-250
> Project: Geronimo
> Type: Bug
> Components: connector
> Versions: 1.0-M2
> Reporter: Simon Godik
> Assignee: David Jencks
> Fix For: 1.0-M5
>
> If a resource adapter indicates a connection has had a fatal error, then the connection manager destroys the managed connection but still attempts to commit/rollback at transaction end. This is bad as the connection has already been destroyed.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-250) Connector tries to commit after connection error
Posted by "David Blevins (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-250?page=all ]
David Blevins updated GERONIMO-250:
-----------------------------------
Fix Version: 1.0
(was: 1.0-M5)
> Connector tries to commit after connection error
> ------------------------------------------------
>
> Key: GERONIMO-250
> URL: http://issues.apache.org/jira/browse/GERONIMO-250
> Project: Geronimo
> Type: Bug
> Components: connector
> Versions: 1.0-M2
> Reporter: Simon Godik
> Assignee: David Jencks
> Fix For: 1.0
>
> If a resource adapter indicates a connection has had a fatal error, then the connection manager destroys the managed connection but still attempts to commit/rollback at transaction end. This is bad as the connection has already been destroyed.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-250) Connector tries to commit after connection error
Posted by de...@geronimo.apache.org.
Message:
The following issue has been re-assigned.
Assignee: David Jencks (mailto:david@coredevelopers.net)
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-250
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-250
Summary: Connector tries to commit after connection error
Type: Bug
Status: Open
Priority: Major
Project: Apache Geronimo
Components:
connector
Versions:
1.0-M2
Assignee: David Jencks
Reporter: Simon Godik
Created: Tue, 22 Jun 2004 6:29 PM
Updated: Sun, 18 Jul 2004 4:01 PM
Description:
If a resource adapter indicates a connection has had a fatal error, then the connection manager destroys the managed connection but still attempts to commit/rollback at transaction end. This is bad as the connection has already been destroyed.
---------------------------------------------------------------------
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] Updated: (GERONIMO-250) Connector tries to commit after connection error
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-250?page=all ]
David Jencks updated GERONIMO-250:
----------------------------------
Fix Version: 1.x
(was: 1.0)
> Connector tries to commit after connection error
> ------------------------------------------------
>
> Key: GERONIMO-250
> URL: http://issues.apache.org/jira/browse/GERONIMO-250
> Project: Geronimo
> Type: Bug
> Components: connector
> Versions: 1.0-M2
> Reporter: Simon Godik
> Assignee: David Jencks
> Fix For: 1.x
>
> If a resource adapter indicates a connection has had a fatal error, then the connection manager destroys the managed connection but still attempts to commit/rollback at transaction end. This is bad as the connection has already been destroyed.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira