Aborted connections when using node.js/mysql connectionPool

Question

var mysql      = require('mysql');
var mysqlPool  = mysql.createPool({
  host    : 'localhost',
  user    : 'nodejs',
  password: '',
  database: 'nodejs'
});


// somewhere inside a method:
mysqlPool.getConnection(function(err, connection) {
    // do some queries

    connection.release();
});

I don't see any warnings in the output, but on the MySQL server I see aborted connections since testing with this node.js code.

Do I have to close the connection pool when I stop the node.js app?

If yes, how?

Rodrigo Medeiros · Accepted Answer · 2014-05-29 02:09:05Z

1

If you're closing you're node.js app with a Ctrl+C command, you could close your connection pool on the SIGINT event:

process.on('SIGINT', function() {
  mysqlPool.end(function (err) {
    /* Since you're overriding the default behavior of SIGINT,
       you have to force your app to exit. You can pass it as 
       a callback to the end() function. */
    process.exit(0);
  });
});

But you could also configure your MySQL server to close idle connections, setting the server variables wait_timeout and/or interactive_timeout.

It's up to you to decide what best fits your needs.

edited May 29, 2014 at 2:09

answered May 28, 2014 at 17:15

Rodrigo Medeiros

7,8724 gold badges45 silver badges55 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Daniel W. Over a year ago

Yea, I close the app with CTRL+C. This solution sounds exactly like what I was looking for, can try it 2moz, thanks in advance!

Collectives™ on Stack Overflow

Aborted connections when using node.js/mysql connectionPool

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related