ResourceRequest timed out
See original GitHub issueNode: 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' }
Issue Analytics
- State:
- Created 6 years ago
- Reactions:13
- Comments:74 (7 by maintainers)
Top Results From Across the Web
Sequelize: TimeoutError: ResourceRequest timed out
My Express app running on node 6.11 with Sequelize 4.5.0 will sometimes throw TimeoutError: ResourceRequest timed out , on operations that ...
Read more >Debugging ResourceRequest Timed out error in Sequelize
While working on a project that involves building a small analytics platform using PostgreSQL, I ran into the ResourceRequest timed out ...
Read more >TimeoutError: ResourceRequest timed out #7884 - GitHub
I cannot reproduce the error. Obviously there was a timeout in connecting to the DB server, it doesn't look like a bug in...
Read more >MySQL : Sequelize: TimeoutError: ResourceRequest timed out
MySQL : Sequelize: TimeoutError: ResourceRequest timed out [ Beautify Your Computer : https://www.hows.tech/p/recommended.html ] MySQL ...
Read more >nodejs/node - Gitter
Unhandled rejection TimeoutError: ResourceRequest timed out at ... -samples\mm-node\node_modules\generic-pool\lib\ResourceRequest.js:58:17) at Timeout.bound ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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.
I’m also getting this error. This affects our production environment rather badly every other 2 days (and the we have to restart our service). Is there any more news on this?