[
https://issues.apache.org/jira/browse/PROTON-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269208#comment-16269208
]
Andrew Stitcher commented on PROTON-1700:
-----------------------------------------
Incidentally - this bug only exhibits when the stop happens *after* the
connection error has been reported. This is why you may see the test program
exit under some conditions.
The conditions for the bug are that the run loop needs to have something going
on at the point of the stop command to cause it to carry on rescheduling the
connect attempts. If the stop happens before the first reported failure then
the run loop has nothing to keep it going and will just stop.
> Reconnecting container does not respond to stop
> -----------------------------------------------
>
> Key: PROTON-1700
> URL: https://issues.apache.org/jira/browse/PROTON-1700
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
> Affects Versions: proton-c-0.18.1
> Reporter: Justin Ross
> Assignee: Andrew Stitcher
> Labels: reproducer
> Fix For: proton-c-0.19.0
>
> Attachments: reconnect-and-stop.cpp
>
>
> Calling stop from another thread fails to terminate a container when it is
> attempting to reconnect.
> The attached reproducer never exits (or mostly never exits - I may have seen
> it do it once). I believe it should.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
