PROTOCOL_SEQUENCE_TIMEOUT in Node v4.2

[TooBug]

[Error: Query inactivity timeout]
PROTOCOL_SEQUENCE_TIMEOUT

I'm using this image https://hub.docker.com/r/mhart/alpine-node/, so not so sure if it's node-mysql's problem. Need confirm.

[kerihenare]

Definitely seems to be an issue between node-mysql and Node 4.2.0. The following script works fine in 4.1.2 but gets a connection timeout in 4.2.0.

var mysql      = require('mysql');

var connection = mysql.createConnection({
    host:           'localhost',
    user:           'user',
    password:       'password',
    database:       'database'
});

connection.connect();

connection.query('SELECT 1 + 1 AS solution', (error, rows, fields) => {
    if (error) {
        return console.log(error);
    }

    console.log('The solution is: ', rows[0].solution);
});

connection.end();

[dougwilson]

By definition, 4.1.0 to 4.2.0 should be backwards-compatible. Please file a bug against Node.js for this so we can track here.

[dougwilson]

Seems likely to be the bug nodejs/node#3331

[dougwilson]

I'll try to investigate the regression from Node.js 4.2 that is causing this sometime this week unless someone gets to it first :)

[fengmk2]

nodejs/node@63644dd introduced this bug.

Workaround: set Sequence._idleTimeout = -1 instead of undefined https://github.com/felixge/node-mysql/blob/master/lib/protocol/sequences/Sequence.js#L30

[dougwilson]

Looks like there is going to be a 4.2.1 tomorrow (nodejs/node#3337), so it should be quick enough we don't need to introduce some kind of work-around for the bug.

[fengmk2]

@dougwilson indeed.

[RobinQu]

I should google before debugging this exception.......

[nurrony]

@RobinQu I am also a victim of this.. Want to be updated as soon as this issue is closed

[Meekohi]

Thanks, "everyone's favourite JavaScript feature". Having this issue also.

[clintfenton]

+1

[clintfenton]

Temporary fix from @fengmk2 worked for me to get things going again. Looking forward to the repaired release.

[Jaykah]

nodejs/node#3337 has been merged

[dougwilson]

Yes, and 4.2.1 has been released: https://nodejs.org/en/blog/release/v4.2.1/

[Wikunia]

I have the same error in v4.2.1 and I had to change _idleTimeout to -1 to make it work.

[AdriVanHoudt]

it should work on undefined see https://github.com/nodejs/node/pull/3331/files

[Wikunia]

Thanks, not sure why this happens but well there is a fix, so it's okay for me.

[AdriVanHoudt]

yeah it landed in 4.2.1 so it should work

[Meekohi]

I can confirm v4.2.1 fixed this for me.

[dougwilson]

Hi everyone, if you are getting this only in Node.js 4.2.0, it's because that version had a regression in timer code. You have to either downgrade to 4.1.0 or upgrade to 4.2.1.