[
https://issues.apache.org/jira/browse/PROTON-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16819035#comment-16819035
]
Andrew Stitcher commented on PROTON-2026:
-----------------------------------------
It seems that the entire cause of this issue is that a failed connect no longer
produces the TRANSPORT_CLOSED event.
The code for reconnect when the event is received is still present, but the
event does not fire in this case.
> reconnect is broken
> -------------------
>
> Key: PROTON-2026
> URL: https://issues.apache.org/jira/browse/PROTON-2026
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Affects Versions: proton-c-0.28.0
> Reporter: Gordon Sim
> Assignee: Andrew Stitcher
> Priority: Blocker
> Fix For: proton-c-0.28.0
>
>
> E.g. try running simple_recv.py against a server that is not there. Up to
> 0.27.0 it would keep trying, on master now it exists with a socket error.
> Also, likely related, up to 0.27.0 you would always get an
> on_transport_closed in this case, but on master you no longer do.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
