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
There seems to be no direct method to manually disconnect. When invoking the disconnect method on the client struct, it does trigger an actual disconnection.
However, the reconnection mechanism remains active, which results in the client attempting to reconnect immediately after disconnection.
This issue can be circumvented by setting the reconnect attribute to false in the ClientBuilder, but this solution is not viable for my use case. I need the client to automatically reconnect in the event of an accidental disconnection, not a manual one.
Is there a way to manually disconnect the client such that it doesn't attempt to reconnect, while still retaining the automatic reconnection capability in cases of unintentional disconnections?
The text was updated successfully, but these errors were encountered:
Will this also allow to kill the connection and reinstate with new authentication credentials? Currently we want to be able to disconnect and restart with new authentication parameters, but still reconnect on disconnect events. Will this allow that flow?
Unable to Disconnect Manually
There seems to be no direct method to manually disconnect. When invoking the
disconnect
method on the client struct, it does trigger an actual disconnection.However, the reconnection mechanism remains active, which results in the client attempting to reconnect immediately after disconnection.
This issue can be circumvented by setting the reconnect attribute to false in the ClientBuilder, but this solution is not viable for my use case. I need the client to automatically reconnect in the event of an accidental disconnection, not a manual one.
Is there a way to manually disconnect the client such that it doesn't attempt to reconnect, while still retaining the automatic reconnection capability in cases of unintentional disconnections?
The text was updated successfully, but these errors were encountered: