[ 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
