On 03/04/2019 11:05 pm, Andrew Stitcher wrote:
On Wed, 2019-04-03 at 22:58 +0100, Gordon Sim wrote:
On 03/04/2019 10:50 pm, Andrew Stitcher wrote:
On Wed, 2019-04-03 at 22:02 +0100, Gordon Sim wrote:
It looks like the reconnect capability in the python client is
broken
on
master. Is this a known issue?
Any chance of some more details or a reproducer?
Just run any of the examples either against a port with no broker,
or
kill the broker after client has connected. On 0.26.0 the client
will
keep trying to reconnect. On master it exits immediately with a
socket.error.
Really? the previous behaviour was to retry without bound? I'm not
surprised I didn't replicate that behaviour - for the simplest examples
it seems wrong. Certainly not what I would expect.
It was debated quite a bit many years ago. It has been that way for a
long, long time. As far as I can tell it doesn't work at all anymore,
even if explicitly requested i.e. it is not simply a change in the
default behaviour.
How was the retry previously achieved?
It handles the transport closed event. There is a Connector class in
_reactor.py that controls it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
