ResourceRequest timed out

[munir131]

Node: 6.9.1
configuration:

pool: {
    max: 100,
    min: 1,
    idleTimeoutMillis: 15000
}

I am getting this error when there is less traffic or there is gap between requests.

error:  { TimeoutError: ResourceRequest timed out
        at ResourceRequest._fireTimeout (/home/munir/node-workspace/server/node_modules/generic-pool/lib/ResourceRequest.js:62:17)
        at Timeout.bound (/home/munir/node-workspace/server/node_modules/generic-pool/lib/ResourceRequest.js:8:15)
        at ontimeout (timers.js:365:14)
        at tryOnTimeout (timers.js:237:5)
        at Timer.listOnTimeout (timers.js:207:5) name: 'TimeoutError' }

[labs20]

+1, and its random.

Please any help?

[glebson1]

If you're using transactions in your calls it seems to be an issue. Improper usage of them makes pool get stacked. Try to get rid off them.

[munir131]

@glebson1 Thanks for your reply. But, I am not getting how it is affecting to it?

[munir131]

@patriksimek Can you give me any hint that can help?

[tkunanuntakij]

I got a similar problem with ESOCKETTIMEOUT. It happened when I deploy my app and my docker install the latest version of tedious (v2.3.1, I think) as its dependency. When I ran my batch jobs which used quite a large and complex query, it made a lot of timeout which didn't happen before in the previous version. While I don't know how write reproduce steps without using the same database and query, My current solution is to force its dependency to install tedious (v2.1.1) using npm-shrinkwrap.json that I made from my local repo.

[munir131]

@gentlerainsky Thanks. I will try it.

[munir131]

@gentlerainsky I tried by using tedious (v1.x) But still getting resourceRequest timeout issue.

[anton-bot]

Sequelize fixed this bug. Please just reference their pull request. This is a huge issue that prevents normal operation!

sequelize/sequelize#8815

[munir131]

@catcher-in-the-try They did same thing which is already done by some developers in pending PR(coopernurse/node-pool#198 & coopernurse/node-pool#221) of generic-pool. So, looks like there is issue in generic-pool

[JankiGadhiya]

Guys, Any updates in this? My production is heading to a big event today and I am in a big mess because of this issue.

[labs20]

I had a really hard time on my customer with this too. Managed to reduce the damage somehow with the config below, but its urgent to fix this one.
pool: { max: 100000, min: 1, idleTimeoutMillis: 50, evictionRunIntervalMillis: 5, softIdleTimeoutMillis: 5 }

[munir131]

@labs20 Are you not facing more issue with this configuration? I think 50ms timeout will create this issue more frequently. Also, It will increase chances of this error.

[labs20]

Well, at least on my customer server it seems to have reduced the problem.

[munir131]

@catcher-in-the-try @labs20 It is working fine for me after I used https://github.com/munir131/node-mssql

[anton-bot]

@munir131 I couldn't figure out how to use, it doesn't seem to be documented or published to NPM.