[jira] [Commented] (QPID-6202) Closing an AMQProtocolEngine can leave it in an inconsistent state if an AMQChannel fails to close

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-6202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190371#comment-14190371 ] 

ASF subversion and git services commented on QPID-6202:
-------------------------------------------------------

Commit 1635548 from [~k-wall] in branch 'qpid/trunk'
[ https://svn.apache.org/r1635548 ]

QPID-6202: [Java Broker] Ensure AMQProtocolEngine#closeSession() completes closure even if AMQChannel fails to close cleanly

> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org