You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry for the slow response. Up to and including current published version 2.4.x the behaviour is to allow infinite number of queued requests. This means that calls to acquire will always be accepted and queued up for allocation. This can lead to deadlocking in some situations if your application never returns resources to the pool
There are PRs in progress #125 and #127 to allow acquire calls to fail if the pool is full, and/or timeout acquire calls if they aren't fulfilled in a given time frame, and I intend to add a feature to allow configuring the max number of "waiting" acquire calls.
Let me know if this helps or you have any more questions.
This pretty much answers, what I was looking for. Thx.
In fact, I did notice those PRs after raising this question here.
My +1 on the timeout implementation and maxWaitingClients options. Looking forward to those features getting merged.
For now, I have implemented the acquireTimeout feature myself, for the use case that I am solving.
max
= 1. Looks like i am not getting an error here.What is the expected behavior?.
The text was updated successfully, but these errors were encountered: