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/12/07 01:29:20 UTC
[jira] Created: (GERONIMO-2632) Connection errors can result in
infinite loop
Connection errors can result in infinite loop
---------------------------------------------
Key: GERONIMO-2632
URL: http://issues.apache.org/jira/browse/GERONIMO-2632
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: connector
Affects Versions: 2.0
Reporter: David Jencks
Assigned To: David Jencks
Fix For: 2.0
We have a GeronimoConnectionEventListener that always tries to return the connection with a DESTROY action. Well, if the connection is sufficiently broken, trying to close it might cause another ConnectionError event...... leading to infinite recursion.
I'm putting in a flag so only the first ConnectionError event causes the connection to get destroyed.
Also, there isn't really any point in calling cleanup on a managed connection we're about to destroy. Just another way to try to provoke another connection error.
--
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] Closed: (GERONIMO-2632) Connection errors can result in
infinite loop
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2632?page=all ]
David Jencks closed GERONIMO-2632.
----------------------------------
Resolution: Fixed
Fixed in rev 483310. in trunk only
> Connection errors can result in infinite loop
> ---------------------------------------------
>
> Key: GERONIMO-2632
> URL: http://issues.apache.org/jira/browse/GERONIMO-2632
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: connector
> Affects Versions: 2.0
> Reporter: David Jencks
> Assigned To: David Jencks
> Fix For: 2.0
>
>
> We have a GeronimoConnectionEventListener that always tries to return the connection with a DESTROY action. Well, if the connection is sufficiently broken, trying to close it might cause another ConnectionError event...... leading to infinite recursion.
> I'm putting in a flag so only the first ConnectionError event causes the connection to get destroyed.
> Also, there isn't really any point in calling cleanup on a managed connection we're about to destroy. Just another way to try to provoke another connection error.
--
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