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)" <ji...@apache.org> on 2006/10/28 10:34:18 UTC
[jira] Created: (GERONIMO-2529) Connector framework must not
re-close connections that are closed in a synchronization afterCompletion
Connector framework must not re-close connections that are closed in a synchronization afterCompletion
------------------------------------------------------------------------------------------------------
Key: GERONIMO-2529
URL: http://issues.apache.org/jira/browse/GERONIMO-2529
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: connector
Affects Versions: 1.2
Reporter: David Jencks
Assigned To: David Jencks
Fix For: 1.2
There's a hole in the connection tracking logic so that if an application closes a connection in a synchronization afterCompletion it is still tracked in the ManagedConnectionInfos but it is returned to the pool. A moment later geronimo's afterCompletion fires and returns the connection a second time... quickly filling the pool with the same connection.
--
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] Resolved: (GERONIMO-2529) Connector framework must not
re-close connections that are closed in a synchronization afterCompletion
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2529?page=all ]
David Jencks resolved GERONIMO-2529.
------------------------------------
Resolution: Fixed
fixed in rev 468719. This could use a unit test.
> Connector framework must not re-close connections that are closed in a synchronization afterCompletion
> ------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2529
> URL: http://issues.apache.org/jira/browse/GERONIMO-2529
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: connector
> Affects Versions: 1.2
> Reporter: David Jencks
> Assigned To: David Jencks
> Fix For: 1.2
>
>
> There's a hole in the connection tracking logic so that if an application closes a connection in a synchronization afterCompletion it is still tracked in the ManagedConnectionInfos but it is returned to the pool. A moment later geronimo's afterCompletion fires and returns the connection a second time... quickly filling the pool with the same connection.
--
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