-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
client SYNC_CONNECTED despite being disconnected from the server for longer than session timeout #13
Comments
Is there any plan to fix this? We always see this when the remote server is powered off and the client doesn't get any response from server. |
Would also like to know if this can be fixed. |
I will take a look this weekend. |
Hi alexguan, I was also looking at this issue. Basically it happens in two cases
I have worked on a fix for this. Idea is to use the readTimeout (2/3 * sessiontimeout). If with in this time if we have not seen any data, then we can destroy the socket on client side. this will reconnect to other available servers.Since, we are sending ping every 1/3_sessiontimeout, we should be expecting a read response within 2/3_sessiontimeout. I saw "C" Implementation and they have this timeout handling. Let me know what you think of this patch. diff:
|
hey , please let me know if the patch is good enough or you have a better one? |
Any update on this? |
It's a blocking issue to me. Any plan on fixing this issue? |
…isconnected from the server
…isconnected from the server
Apply fix to #13: Client stays in SYNC_CONNECTED state when disconnec…
Client stays in SYNC_CONNECTED state when disconnected from the server for longer than its session timeout. I expected DISCONNECTED state after second 3 or 5 below:
The text was updated successfully, but these errors were encountered: