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
Consider adding property like supportsKeepAliveReconnectTimeout on client, when it is true then on client KeepAlive can stop to reconnect once reconnect timestamp great than the timeout, and stop the connection.
#825
Closed
Xiaohongt opened this issue
Oct 19, 2012
· 1 comment
Currently when the network become disconnected, the client KeepAlive will try to reconnect again again forever, but on server side when the connection timeout, server close the connection, but the client still try to reconnect until the network get connected then client disconnect the connection.
If we add property like supportsKeepAliveReconnectTimeout on client, by default we can set it to false, so client still have the same old behavior.
When supportsKeepAliveReconnectTimeout set to true, then client KeepAlive can stop to reconnect once reconnect timestamp great than the timeout, and the timeout by default we can set the value same as the server connection timeout or bigger.
The text was updated successfully, but these errors were encountered:
Currently when the network become disconnected, the client KeepAlive will try to reconnect again again forever, but on server side when the connection timeout, server close the connection, but the client still try to reconnect until the network get connected then client disconnect the connection.
If we add property like supportsKeepAliveReconnectTimeout on client, by default we can set it to false, so client still have the same old behavior.
When supportsKeepAliveReconnectTimeout set to true, then client KeepAlive can stop to reconnect once reconnect timestamp great than the timeout, and the timeout by default we can set the value same as the server connection timeout or bigger.
The text was updated successfully, but these errors were encountered: