Debugging stray uncaught exceptions (ECONNRESET) in a node cluster

Question

In my node.js app which uses the cluster module, I'm intermittently seeing errors like this:

events.js:71
        throw er; // Unhandled 'error' event
              ^
Error: read ECONNRESET
    at errnoException (net.js:863:11)
    at TCP.onread (net.js:524:19)

This brings down my whole app, and so far the only way I've been able to deal with these is by binding a process.on('uncaughtException'). I'd like to figure out the underlying cause, but the above stack trace is pretty useless.

Is there some way to figure out what's causing these exceptions?

I should note that I'm seeing these only in the cluster master, not the workers, which leads me to suspect that they have something to do with the way the cluster modules does its magic in distributing connections to workers.

possible duplicate of [How to debug a socket hang up error in NodeJS?](http://stackoverflow.com/questions/10814481/how-to-debug-a-socket-hang-up-error-in-nodejs) — e-sushi, Jul 14 '13 at 08:53

score 1 · Answer 1 · edited May 23 '17 at 12:00

1

This answer was helpful: https://stackoverflow.com/a/11542134/233370

Basically, I installed longjohn and was then able to get the full async stack trace to figure out the underlying cause (rabbit.js in my case).

edited May 23 '17 at 12:00

Community

1
1

answered Jun 05 '13 at 22:07

Matt Zukowski

4,469
4
37
38

score 0 · Answer 2 · answered Oct 27 '15 at 16:12

It seems that express enabled keep-alive by default. In order to close connection after response you can add res.set("Connection", "close");

Alternatively you can add a middleware in your app to close connection after each response:

 app.use(function(req, res, next) {
         res.set("Connection", "close");
         next();
     });

Debugging stray uncaught exceptions (ECONNRESET) in a node cluster

2 Answers2