Chrome disconnecting after 5 minutes

[Velocedge]

I'm using the chat example and with Chrome 24, it connects, sends, and receives fine... for a while. After about five minutes the OnDisconnect event in the server fires from the Chrome client. However, I don't get a close event in the browser.

If I stop the server, the websocket.onclose event fires so I know it's hooked up properly in the browser. If I got the onclose in the browser, I could reconnect but it doesn't know that it's been disconnected.

This works fine (no timeout) in IE10. Just ran more tests and it times out in FF16 and FF18 too. Client is straight Javascript.

[vbguyny]

Do you know if this happens in Safari? This would let us know if the problem is in webkit vs. a chromium issue. Also does Chrome raise any javascript errors after it disconnects?

[Velocedge]

It times out on Safari 5.1 too. No errors are raised on disconnect... in fact, neither the onClose or onError events fire.

[vbguyny]

I am not able to duplicate your issue... tried for 15 minutes and didn't have my connection get dropped. However I am testing using the my custom version of the websocket which uses SSL. Download it here: https://github.com/vbguyny/Alchemy-Websockets and see if you can duplicate the issue.

[Lakritzator]

The "5" minutes is the time-out, you can change it.
The problem is that on the server when a timeout occurs I can see a OnDisconnect being called, but afterwards the connection is still in some weird state. A client can still send something (once?) and never gets an error or disconnect.

I found a similar bug here: #89
But this repository seems to be a bit "dead"... no changes for 11 months.

Here is a more active repository (fork): https://github.com/steforster/Alchemy-Websockets