handleMessage seems to kill the process if a promise is rejected in the callback function

[jcollum-cambia]

const Consumer = require('sqs-consumer');

const app = Consumer.create({
    queueUrl: config.aws.delta.queueUrl,
    handleMessage: (message, done) => {
      logger.debug(message);
      processor.process(message).then((result) => {
        logger.trace(`Message processed.`);
        done();
      }).catch((err) => {
        logger.error("Failed to handle message", message);
      // uncomment next line to get it to work without bailing  
      //done();
      });
    }
  });


... 
app.start();

If I uncomment done() then it will work. But I often want the message to stay on the queue -- maybe I couldn't connect to the database momentarily and that's why it failed. As the code is, if I hit that .catch and don't call done() the process mysteriously exits, even if I have an uncaughtException/unhandledRejection listener on the process.

"sqs-consumer": "^3.6.1",

Node 6

[Sicria]

Have you tried calling done(err); in your catch?

Calling done(err) with an error object will cause the message to be left on the queue.

[jcollum-cambia]

That did it, thanks. Still there's the issue of not doing that crashing my process. No warnings/errors or anything, just a full stop.

[Sicria]

You could add this to catch any unhandled rejections that occur.

process.on('unhandledRejection', error => logger.crit('Unhandled Rejection', error));

[nspragg]

@Sicria - thanks for your suggestions.

@jcollum-cambia - "rejected in callback". Are you referring to an explicit call to reject or is an exception being thrown?

[nspragg]

I'm closing this issue due to inactivity. Will reopen, if you wish to discuss further.