You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my test, once the server forces a disconnection, the local conn will still be set and all client operations will fail. mb.connect() doesn't get triggered in this case.
I couldn't find anything regarding this in the library. I had to check client calls for errors and manually close and connect.
Is this intended? Is there a better way to achieve this (e.g., check for broken pipe errors and reconnect)?
The text was updated successfully, but these errors were encountered:
Prushka
changed the title
How to tell if server disconnects? I couldn't find any mechanism.
How to tell if server closes the connection? I couldn't find any mechanism.
Aug 8, 2022
Prushka
changed the title
How to tell if server closes the connection? I couldn't find any mechanism.
How to tell if server closes the connection?
Aug 8, 2022
In my test, once the server forces a disconnection, the local
conn
will still be set and all client operations will fail.mb.connect()
doesn't get triggered in this case.I couldn't find anything regarding this in the library. I had to check client calls for errors and manually close and connect.
Is this intended? Is there a better way to achieve this (e.g., check for broken pipe errors and reconnect)?
The text was updated successfully, but these errors were encountered: