Another socket error Error: read ECONNRESET

[simonmorley]

We're getting some really odd errors on disconnect that we can't figure out. Looks like the server's not noticing the disconnect or handling it correctly. If we kill the client we get this:

info  - socket error Error: read ECONNRESET
at errnoException (net.js:901:11)
at onread (net.js:556:19)

---

at Readable.on (_stream_readable.js:679:33)
at Transport.setHandlers (node_modules/socket.io/lib/transport.js:115:15)
at Transport.handleRequest (node_modules/socket.io/lib/transport.js:70:10)
at Transport (node_modules/socket.io/lib/transport.js:31:8)
at new WebSocket (node_modules/socket.io/lib/transports/websocket/hybi-16.js:59:13)
at new WebSocket (node_modules/socket.io/lib/transports/websocket.js:31:17)
at Manager.handleClient (node_modules/socket.io/lib/manager.js:662:19)
at Manager.handleUpgrade (node_modules/socket.io/lib/manager.js:618:8)

If we manually disconnect the client's connection, we see nothing in the logs. Very strange.

We're not using the standard js client, instead we have a c++ one that runs on an embedded device. The strange thing is that it runs on all the devices we've tested on apart from one without problem

We're running Node v0.10.13 and Socket.io 0.9.12

-- Slight Edit --

I forgot to mention that the socket will connect and disconnect the first time correctly.. However, if we reconnect the client WITHOUT restarting the server, we start seeing these errors. After the first disconnection, we only see:

info  - socket error Error: read ECONNRESET
at errnoException (net.js:901:11)
at onread (net.js:556:19)

at fireErrorCallbacks (net.js:440:15)
at Socket._destroy (net.js:472:3)
at onread (net.js:556:10)

[gagahjt]

socket error Error: read ECONNRESET
node: v0.10.15
socket.io :0.9.16

when using ie browser disconnected..

[piuccio]

When you disconnect IE you might be experiencing something similar to testem/testem#294.
Which is caused by this change in node 0.10

Guessing :)

[jakub-g]

Socketio 0.9.16, Node 0.10.20@Win7 (was fine everywhere under 0.8.*)

It's happening for me in IE8, IE9 (checked with manual disconnect) and PhantomJS 1.9.1/1.9.2 (checked with calling disconnect() from the client, or killing the phantom child process on the server side).

IE10@Win8, Firefox, Chrome, and Safari 5.1.7 do not provoke this exception.

The stack trace using longjohn is slightly different in IE and Phantom though (stack is before the red error line here), but boils down to the same issue.