[
https://issues.apache.org/jira/browse/PROTON-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965421#comment-14965421
]
ASF subversion and git services commented on PROTON-1024:
---------------------------------------------------------
Commit d72f161d1d19aad55622adb6469a98ab9f396c1a in qpid-proton's branch
refs/heads/master from [~gsim]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=d72f161 ]
PROTON-1024: fix handling of disconnection for BlockingConnection
> Disconnect during close not handled correctly in BlockingConnection
> -------------------------------------------------------------------
>
> Key: PROTON-1024
> URL: https://issues.apache.org/jira/browse/PROTON-1024
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Affects Versions: 0.10
> Reporter: Gordon Sim
> Assignee: Gordon Sim
> Fix For: 0.11
>
>
> If the connection is lost (or aborted) after issuing the close, but before
> the peer responds, the BlockingConnection gets stuck in an endless loop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
