-
Notifications
You must be signed in to change notification settings - Fork 90
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.subscribe() keeps creating new connections #7
Comments
because the client default timeout is 30s, and the server default timeout is 120s. you can set the client timeout more than 120s to fixed problem. |
Thank you for your reply, I've extended the client timeout to 1 day, it stops creating new connections. But look at the 1st screenshot, it indicates that the old connections are not closed (status = PS. The term |
When timeout on client, the connection will not to be closed, because maybe some other requests on this connection too. |
The problem is, by default settings, I guess this should be a architecture issue, but I don't have enough time to investigate and prove this. Sets the client timeout to 1 day or some big number is just a workaround. I implemented a manual but real heartbeat in my application, by pushing an empty string to the subscribers every minute. |
Yes, you are right. I will try to fix this problem in next version. |
I see this in Chome devtool >> Network:
Client script:
Server script:
The text was updated successfully, but these errors were encountered: