pong on closed connection error #30

Closed
danielwaterworth opened this Issue Feb 24, 2012 · 4 comments

2 participants

@danielwaterworth

I keep seeing this error:

/home/deploy/node_modules/ws/lib/WebSocket.js:153
  if (this.readyState != WebSocket.OPEN) throw new Error('not opened');
                                         ^
Error: not opened
    at WebSocket.pong (/home/deploy/node_modules/ws/lib/WebSocket.js:153:48)
    at Receiver.<anonymous> (/home/deploy/node_modules/ws/lib/WebSocket.js:539:10)
    at Receiver.emit (events.js:70:17)
    at Receiver.<anonymous> (/home/deploy/node_modules/ws/lib/Receiver.js:523:12)
    at /home/deploy/node_modules/ws/lib/Receiver.js:518:31
    at Receiver.expectData (/home/deploy/node_modules/ws/lib/Receiver.js:129:5)
    at Receiver.<anonymous> (/home/deploy/node_modules/ws/lib/Receiver.js:517:14)
    at Receiver.<anonymous> (/home/deploy/node_modules/ws/lib/Receiver.js:500:30)
    at Receiver.<anonymous> (/home/deploy/node_modules/ws/lib/Receiver.js:193:19)
    at Receiver.add (/home/deploy/node_modules/ws/lib/Receiver.js:93:24)
@einaros

Do you happen to have a ping on an interval?

@danielwaterworth

@einaros, No, my code doesn't call either ping or pong. (Obviously the server that I'm connecting to does.)

@einaros

Rater rude of the server to ping you and then disconnect. But point taken, I'll mask the error from automated pongs.

@danielwaterworth

I think the connection was closed on my side.

@einaros einaros closed this in 8c3f6d7 Feb 28, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment