reconnecting-websocket icon indicating copy to clipboard operation
reconnecting-websocket copied to clipboard

Firefox 26 does not reconnect after server bounce

Open logan70389 opened this issue 12 years ago • 1 comments

This could be browser bug - I'm not sure. I ran a test using Internet Explorer, Firefox 26, and Chrome. I had all 3 clients working as expected with text messages. I then bounced the server (Glassfish 4). Internet Explorer and Chrome reconnected. Firefox did not. I ran the test twice - same results.

Firefox Log: The connection to ws://127.0.0.1:8080/ReconnectingWebSocket/websocket was interrupted while the page was loading. reconnecting-websocket.js:84 18:36:40.705 Firefox can't establish a connection to the server at ws://127.0.0.1:8080/ReconnectingWebSocket/websocket. reconnecting-websocket.js:84 18:36:40.705 The connection to ws://127.0.0.1:8080/ReconnectingWebSocket/websocket was interrupted while the page was loading. reconnecting-websocket.js:84 18:36:44.362 Firefox can't establish a connection to the server at ws://127.0.0.1:8080/ReconnectingWebSocket/websocket.

logan70389 avatar Jan 24 '14 23:01 logan70389

I'm getting a lot of reports about this as well from website visitors, now that I'm using ws node module. Can't really reproduce it myself.

Umkus avatar Sep 29 '17 13:09 Umkus