CODEWITHSUNDEEP
node.jsexit
damien
damien

Reputation: 709

When a Node.js process can exit() directly without triggering other signal events (uncaughtException, SIGINT, SIGTERM...)

I work on an application with a REDIS data store. To maintain the data integrity I would like to cleanup the store on process shutdown.

I created a function handler and bind it (with process.on()) to signal events: uncaughtException, SIGINT, SIGTERM, SIGQUIT and it works well (CTRL+C, process killing, exception, ...).

But I've read that in certain conditions the process can exit directly without triggering the other signal events.

The problem in this particular case is that process.on('exit') handler can only process synchronous tasks.

I made different test to try to kill the process in different ways. And (except with SIGTERM on Windows) I wasn't able to identify the case where process.on('exit') is triggered directly without SIGINT, SIGTERM or other event firing.

So my question is (on Linux system), under what conditions the process can exit directly without firing on of this event: http://nodejs.org/api/all.html#all_signal_events ?

Upvotes: 9

Views: 3840

Answers (2)

Dave Pacheco
Dave Pacheco

Reputation: 850

Indeed. I just meant to point out that Node programs can exit as a result of a signal without having executed a handler (if none was registered). Rereading your post, I see that may be what you meant as well.

Upvotes: -1

DrakaSAN
DrakaSAN

Reputation: 7853

As of now, reading the documentation and doing some research, it seems there is only four way a node.js app exit:

It usually happen someone don t understand the error message from a uncaughtException, and mistakenly believe it is "something else" that killed node.js.

Upvotes: 8

Related Questions