Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Client fails to reconnect if server has timed out client connection. #687

Closed
NTaylorMullen opened this issue Sep 18, 2012 · 3 comments
Closed

Client fails to reconnect if server has timed out client connection. #687

NTaylorMullen opened this issue Sep 18, 2012 · 3 comments
Assignees
@NTaylorMullen
Labels
type: Bug
Milestone
1.0 Alpha 1

Comments

@NTaylorMullen
Copy link
Contributor

Issue: Client Stays in connecting state long enough for server to time out (and drop) the client connection.
Result: When the server comes back online the client attempts to connect and fires the reconnect event to immediately be disconnected because the connection ID does not exist.
@ghost ghost assigned NTaylorMullen Sep 18, 2012
@NTaylorMullen
Copy link
Contributor Author

Repro:

  1. Turn off network adapter for 4 mins (until server times out client).
  2. Turn on network adapater
  3. Infinite cycle of trying to reconnect.

@NTaylorMullen
Copy link
Contributor Author

Linking StackOverflow question that reported the same issue: http://stackoverflow.com/questions/12585090/reconnecting-a-connection-subscribed-to-a-hub-causes-immediate-disconnection/12626691#12626691

NTaylorMullen added a commit that referenced this issue Oct 2, 2012
@NTaylorMullen
Built project and associating commits with issues
d700433 
#666, #469

NOTE: Issue #687 can cause infinite reconnect attempts despite the
client side keep alive.
NTaylorMullen added a commit that referenced this issue Oct 2, 2012
@NTaylorMullen
Fixed SSE client side keep alive check
799c03d 
Also modified server's ungraceful disconnect functionality in the cases
where a client has been timed out on the server.  We now pump down a
disconnect message.

Still need to implement client side keep alive check for the C# client

#469
#687
@Xiaohongt
Copy link
Contributor

verified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@NTaylorMullen NTaylorMullen

Labels
type: Bug
Projects
None yet
Milestone
1.0 Alpha 1
Development

No branches or pull requests
2 participants
@NTaylorMullen @Xiaohongt