[
https://issues.apache.org/jira/browse/QPID-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14005977#comment-14005977
]
Robbie Gemmell commented on QPID-5771:
--------------------------------------
The issue is that the severed connection is not removed from the
ConnectionRegistry when it attempts to clean itself up, because its cleanup
process itself throws an exception after trying to use the connection again to
close the sessions. The ConnectionRegistry then tries to close the connection,
and gets stuck in a loop because the close attempt isn't actually doing
anything (the Connection is already marked closed) that could cause it to be
removed from the registry, so the shutdown hook never completes and it will sit
there as .
The most basic change to resolve the issue is to ensure that the connection is
removed from the registry even if when its own cleanup attempt throws an
exception. Beyond that the cleanup process itself should perhaps be examined.
> java broker doesn't shutdown cleanly...
> ---------------------------------------
>
> Key: QPID-5771
> URL: https://issues.apache.org/jira/browse/QPID-5771
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.28
> Reporter: Gordon Sim
> Assignee: Robbie Gemmell
> Fix For: 0.29
>
> Attachments: Simple.java
>
>
> ... if the connection from the attached test is killed (rather than closing
> cleanly).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
