unhandled exception if socket closes and 'error' is emitted

[jmatthewsr-ms]

The following stack trace shows the exception thrown if the socket fails with ECONNABORTED.

Gist that reproduces the error: https://gist.github.com/3219285

I'm not 100% confident that this fix is in the right place. The uncaught exception appears to be from an unhandled 'error' event from eventemitter. This can occur if Socket._write (net.js:558:19) fails and Socket::_destroy() is called. If there is no callback specified to Socket::_destroy, then the 'error' event is emitted on next tick, which also bypasses any immediate try/catch blocks in Sender::frameAndSend().

events.js:66
throw arguments[1]; // Unhandled 'error' event
^
Error: write ECONNABORTED
at errnoException (net.js:782:11)
at Socket._write (net.js:558:19)
at Socket.write (net.js:517:15)
at Sender.frameAndSend (c:\mydir\node-ws-exception\node_modules\ws\lib\Sender.js:146:22)
at Sender.close (c:\mydir\node-ws-exception\node_modules\ws\lib\Sender.js:43:8)
at WebSocket.close (c:\mydir\node-ws-exception\node_modules\ws\lib\WebSocket.js:89:18)
at Timer. (c:\mydir\node-ws-exception\client.js:35:20)
at Timer.exports.setInterval.timer.ontimeout (timers.js:234:14)

[einaros]

Hmm, I'll dig into this shortly. Sorry for the delay - vacation time and such :)

[starlino]

I have a similar error. Up to date on npm. Was this ever fixed and what is causing this ?? How can it be handled.

Error: connect ECONNABORTED 192.168.137.27:80
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1106:14)
Emitted 'error' event at:
at ClientRequest.req.on (C:\PROJECTS\XYZ\node_modules\ws\lib\websocket.js:554:15)
at ClientRequest.emit (events.js:198:13)
at Socket.socketErrorListener (_http_client.js:392:9)
at Socket.emit (events.js:198:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at process._tickCallback (internal/process/next_tick.js:63:19)