You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2005/02/01 01:21:19 UTC
[jira] Created: (GERONIMO-561) Connection obtained in Synchronization.afterCompletion gets associated w/tx context
Connection obtained in Synchronization.afterCompletion gets associated w/tx context
-----------------------------------------------------------------------------------
Key: GERONIMO-561
URL: http://issues.apache.org/jira/browse/GERONIMO-561
Project: Apache Geronimo
Type: Bug
Components: connector
Versions: 1.0-M3
Reporter: David Jencks
Assigned to: David Jencks
If you have code like this in a Synchronization.afterCompletion:
Connection c = ds.getConnection();
//do something
c.close();
it gets added to the connection tracking of the transaction context that just ended. c.close() returns it to the pool, properly, but the end-of-tx cleanup returns it to the pool a second time.
The connection should not be tracked by the transaction context, the transaction is over.
--
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-561) Connection obtained in Synchronization.afterCompletion gets associated w/tx context
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-561?page=history ]
David Jencks closed GERONIMO-561:
---------------------------------
Resolution: Fixed
Fix Version: 1.0-M4
fixed in rev 149334.
> Connection obtained in Synchronization.afterCompletion gets associated w/tx context
> -----------------------------------------------------------------------------------
>
> Key: GERONIMO-561
> URL: http://issues.apache.org/jira/browse/GERONIMO-561
> Project: Apache Geronimo
> Type: Bug
> Components: connector
> Versions: 1.0-M3
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0-M4
>
> If you have code like this in a Synchronization.afterCompletion:
> Connection c = ds.getConnection();
> //do something
> c.close();
> it gets added to the connection tracking of the transaction context that just ended. c.close() returns it to the pool, properly, but the end-of-tx cleanup returns it to the pool a second time.
> The connection should not be tracked by the transaction context, the transaction is over.
--
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