[
https://issues.apache.org/jira/browse/QPID-6202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-6202:
-----------------------------
Summary: Closing an AMQProtocolEngine can leave it in an inconsistent state
if an AMQChannel fails to close (was: AMQProtocolEngine can leave connection
in inconsistent state of a AMQChannel fails to close)
> Closing an AMQProtocolEngine can leave it in an inconsistent state if an
> AMQChannel fails to close
> --------------------------------------------------------------------------------------------------
>
> Key: QPID-6202
> URL: https://issues.apache.org/jira/browse/QPID-6202
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: 0.31
>
>
> On the 0-8-0-91 path, on closing a connection broker side, if a session fails
> to close cleanly, the connection is left in an inconsistent state. Some of
> its sessions may have been closed, but its close task list remains
> unperformed, and its _closed atomic remains false.
> Furthermore, if a management thread then tries to close the connection
> as_closing is already set true, the management thread believes that a close
> is in flight, so it waits its closure, pooling the _close flag. This will
> never occur, so the management thread will hang.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
