Timeout issues after upgrading to v0.19.10
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 322
- Forks
- 99
- PR merge metrics
- No merged PRs in 30d
Description
After upgrading to Version 0.19.10 we experience Timeout issues with the default value
acquireTimeoutMillis: 1000
within our CAP NodeJS Project.
https://cap.cloud.sap/docs/node.js/databases#pool
TimeoutError: Acquiring client from pool timed out. Please review your system setup, transaction handling, and pool configuration.
With version 0.19.9 everything is fine
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the pool configuration entry in the CAP NodeJS project, focusing on acquireTimeoutMillis: 1000 and the reported pool timeout. Compare behavior between versions 0.19.9 and 0.19.10 using the linked database-pool context; done means identifying the regression or documenting the required configuration change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100