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/07/19 01:09:39 UTC
[jira] Created: (GERONIMO-268) Connection Error handling problems
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-268
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-268
Summary: Connection Error handling problems
Type: Bug
Status: Unassigned
Priority: Major
Project: Apache Geronimo
Components:
connector
Versions:
1.0-M2
Assignee:
Reporter: David Jencks
Created: Sun, 18 Jul 2004 4:07 PM
Updated: Sun, 18 Jul 2004 4:07 PM
Description:
A managed connection that encounters a fatal error and calls ConnectionErrorOccured on the GeronimoConnectionEventListener may not have the resources held by geronimo cleaned up properly.
In particular, if several ejbs have handles to this mc, the connection tracking won't work properly. Only the currently active component (ejb) will have it's handle(s) removed from tracking. When the other handles are disociated or closed, errors are likely, such as putting the destroyed managed connection back into the pool.
---------------------------------------------------------------------
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-268) Connection Error handling problems
Posted by "Prasad Kashyap (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasad Kashyap updated GERONIMO-268:
------------------------------------
Fix Version/s: (was: 2.0-M5)
Verification Required
> Connection Error handling problems
> ----------------------------------
>
> Key: GERONIMO-268
> URL: https://issues.apache.org/jira/browse/GERONIMO-268
> Project: Geronimo
> Issue Type: Bug
> Components: connector
> Affects Versions: 1.0-M2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: Verification Required
>
>
> A managed connection that encounters a fatal error and calls ConnectionErrorOccured on the GeronimoConnectionEventListener may not have the resources held by geronimo cleaned up properly.
> In particular, if several ejbs have handles to this mc, the connection tracking won't work properly. Only the currently active component (ejb) will have it's handle(s) removed from tracking. When the other handles are disociated or closed, errors are likely, such as putting the destroyed managed connection back into the pool.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-268) Connection Error handling problems
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-268?page=all ]
Aaron Mulder updated GERONIMO-268:
----------------------------------
Fix Version: 1.0-M5
Description:
A managed connection that encounters a fatal error and calls ConnectionErrorOccured on the GeronimoConnectionEventListener may not have the resources held by geronimo cleaned up properly.
In particular, if several ejbs have handles to this mc, the connection tracking won't work properly. Only the currently active component (ejb) will have it's handle(s) removed from tracking. When the other handles are disociated or closed, errors are likely, such as putting the destroyed managed connection back into the pool.
was:
A managed connection that encounters a fatal error and calls ConnectionErrorOccured on the GeronimoConnectionEventListener may not have the resources held by geronimo cleaned up properly.
In particular, if several ejbs have handles to this mc, the connection tracking won't work properly. Only the currently active component (ejb) will have it's handle(s) removed from tracking. When the other handles are disociated or closed, errors are likely, such as putting the destroyed managed connection back into the pool.
Environment:
Please review and decide whether this is still an issue and should be fixed for M5. Thanks.
> Connection Error handling problems
> ----------------------------------
>
> Key: GERONIMO-268
> URL: http://issues.apache.org/jira/browse/GERONIMO-268
> Project: Geronimo
> Type: Bug
> Components: connector
> Versions: 1.0-M2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0-M5
>
> A managed connection that encounters a fatal error and calls ConnectionErrorOccured on the GeronimoConnectionEventListener may not have the resources held by geronimo cleaned up properly.
> In particular, if several ejbs have handles to this mc, the connection tracking won't work properly. Only the currently active component (ejb) will have it's handle(s) removed from tracking. When the other handles are disociated or closed, errors are likely, such as putting the destroyed managed connection back into the pool.
--
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-268) Connection Error handling problems
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-268?page=all ]
David Jencks updated GERONIMO-268:
----------------------------------
Fix Version/s: 2.0
(was: 1.x)
> Connection Error handling problems
> ----------------------------------
>
> Key: GERONIMO-268
> URL: http://issues.apache.org/jira/browse/GERONIMO-268
> Project: Geronimo
> Issue Type: Bug
> Components: connector
> Affects Versions: 1.0-M2
> Reporter: David Jencks
> Assigned To: David Jencks
> Fix For: 2.0
>
>
> A managed connection that encounters a fatal error and calls ConnectionErrorOccured on the GeronimoConnectionEventListener may not have the resources held by geronimo cleaned up properly.
> In particular, if several ejbs have handles to this mc, the connection tracking won't work properly. Only the currently active component (ejb) will have it's handle(s) removed from tracking. When the other handles are disociated or closed, errors are likely, such as putting the destroyed managed connection back into the pool.
--
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-268) Connection Error handling problems
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-268?page=all ]
David Jencks updated GERONIMO-268:
----------------------------------
Fix Version: 1.x
(was: 1.0)
> Connection Error handling problems
> ----------------------------------
>
> Key: GERONIMO-268
> URL: http://issues.apache.org/jira/browse/GERONIMO-268
> Project: Geronimo
> Type: Bug
> Components: connector
> Versions: 1.0-M2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.x
>
> A managed connection that encounters a fatal error and calls ConnectionErrorOccured on the GeronimoConnectionEventListener may not have the resources held by geronimo cleaned up properly.
> In particular, if several ejbs have handles to this mc, the connection tracking won't work properly. Only the currently active component (ejb) will have it's handle(s) removed from tracking. When the other handles are disociated or closed, errors are likely, such as putting the destroyed managed connection back into the pool.
--
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-268) Connection Error handling problems
Posted by "David Blevins (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-268?page=all ]
David Blevins updated GERONIMO-268:
-----------------------------------
Fix Version: 1.0
(was: 1.0-M5)
> Connection Error handling problems
> ----------------------------------
>
> Key: GERONIMO-268
> URL: http://issues.apache.org/jira/browse/GERONIMO-268
> Project: Geronimo
> Type: Bug
> Components: connector
> Versions: 1.0-M2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0
>
> A managed connection that encounters a fatal error and calls ConnectionErrorOccured on the GeronimoConnectionEventListener may not have the resources held by geronimo cleaned up properly.
> In particular, if several ejbs have handles to this mc, the connection tracking won't work properly. Only the currently active component (ejb) will have it's handle(s) removed from tracking. When the other handles are disociated or closed, errors are likely, such as putting the destroyed managed connection back into the pool.
--
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-268) Connection Error handling problems
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-268
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-268
Summary: Connection Error handling problems
Type: Bug
Status: Open
Priority: Major
Project: Apache Geronimo
Components:
connector
Versions:
1.0-M2
Assignee: David Jencks
Reporter: David Jencks
Created: Sun, 18 Jul 2004 4:07 PM
Updated: Sun, 1 Aug 2004 1:34 PM
Description:
A managed connection that encounters a fatal error and calls ConnectionErrorOccured on the GeronimoConnectionEventListener may not have the resources held by geronimo cleaned up properly.
In particular, if several ejbs have handles to this mc, the connection tracking won't work properly. Only the currently active component (ejb) will have it's handle(s) removed from tracking. When the other handles are disociated or closed, errors are likely, such as putting the destroyed managed connection back into the pool.
---------------------------------------------------------------------
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