How to handle disconnects?

[pgouv]

Although it seems that there is reconnect ability, it seems that after a connection reset it crashes.
Is there a way to deal with this?

[p-goudet]

Thank you for your report, I will inspect this issue soon.

[pgouv]

@p-goudet I don't know whether it is my configuration but if connection is reset eg: broker is shutdown/restart I get exception and no reconnect

[p-goudet]

A handler was missing to handle exception in case of socket failure (especially when try to read a closed in a socket). I am working on a handler that will call the reconnect() method to the message if the client is configured as persistent. If not the SystemCall error raise by the socket would be raised.

[p-goudet]

@parhs Hello,

I released a new version (1.0.5) which should fix this issue. When the client is configured as persistent, the client would try to reconnect to the message broker after it shutdown (or unexpected socket closing on server side). The client would queue the message that should be sent until the connection is reset. As soon as the connection is reset, the client would resubscribe to the previously subscribed topics.

Could you tell me if the new version solves your issue?