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.

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

staleConnectionTimeout does not work #101

Open
yuanmai opened this issue Sep 9, 2012 · 1 comment
Open

staleConnectionTimeout does not work #101

yuanmai opened this issue Sep 9, 2012 · 1 comment

Comments

@yuanmai
Copy link

yuanmai commented Sep 9, 2012

version: 0.4.14

I created a server using WebServers.createWebServer. I could send & receive messages, when I closed the Chrome tab (websocket client), the WebSocketHandler.onClose method was triggered. But if I disconnect the network of the ws client, it won't trigger the onClose method, or it would take a few minutes to trigger it. According to the source code, the default value of staleConnectionTimeout should be 5 seconds.

@donholly
Copy link

I'm having the same issue currently with 0.4.14. Setting the staleConnectionTimeout (or just leaving it at the default of 5 seconds) seems to have no effect.

If I leave a connection open and send no data across the wire, it never closes itself
If I disconnect my network connection from the client, the server never cleans up the WebSocketConnection

What is the expected behavior here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants