sockjs / websocket in Chrome stays open after laptop comes out of long sleep

[alexkh...@cureatr.com]

I have an app with a sockjs (websocket) connection running in a browser (Chrome) on my laptop. When I re-open the laptop after a long sleep, the connection still appears to be active (onclose hasn't been called, reconnect hasn't triggered), even though it has been correctly dropped on the server (sockjs-tornado) side a long time ago. Any ideas?

Thanks,

Alex

[Serge S. Koval]

SockJS will only trigger onclose for websocket connection when browser will it that connection closed. SockJS does not support heartbeats at the moment.

So far, I did not see such behavior with Chrome and SockJS - Chrome always calls onclose after notebook comes back from sleep.

Serge.

--
You received this message because you are subscribed to the Google Groups "sockjs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sockjs+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[alexkh...@cureatr.com]

Thanks Serge. It appears that this may be somewhat of a known issue: https://code.google.com/p/chromium/issues/detail?id=76358 that is not possible to address without heartbeats.

Until there is good support for heartbeats in sockjs, I will probably just try to detect that the browser has been sleeping and force a reconnect in that case.

Alex

[Eric Mill]

FWIW, implementing a heartbeat yourself isn't the worst. You have to do a small repeating timeout for each client, and to do it both client- and server-side. JavaScript's setInterval is pretty much all you need.

--

twitter.com/konklone | sunlightfoundation.com | awesomefoundation.org

[alexkh...@cureatr.com]

That's what I ended up doing - pushed it live, and it seems to work OK. Thanks for the pointers!