That way you can log the error with more information. To make it not throw, put a listener on it and handle it yourself. Technically, in node, whenever you emit an 'error' event and no one listens to it, it will throw. Use longjohn, you get long stack traces that will contain the async operations. Quick and dirty solution for development:
Instacode setup socket error 0 how to#
You could look at the API server logs to see if it complains about something.īut since you are also looking for a way to check the error and potentially debug the problem, you should take a look at " How to debug a socket hang up error in NodeJS?" which was posted at stackoverflow in relation to an alike question. This is most probably due to one or more application protocol errors. "ECONNRESET" means the other side of the TCP conversation abruptly closed its end of the connection. You might have guessed it already: it's a connection error. Here I serve the flash socket policy file: net = require("net") Seems that this one catches the error: process.on('uncaughtException', function (err) This is the error with Node v0.10.11: events.js:72Įrror: read ECONNRESET //alternatively it s a 'write'Įrror: Forever detected script exited with code: 8Įrror: Forever restarting script for 2 timeĪdded both socket.io client error handler and the uncaught exception handler. Just using websockets and flashsockets transports. The problem is that restarting Express kicks my users out of their rooms
The node process is wrapped in forever and it restarts itself immediately.
I'm running an Express.js application using Socket.io for a chat webappĪnd I get the following error randomly around 5 times during 24h.
0 kommentar(er)
