Sampath,
On 8/6/21 08:37, Sampath Rajapakshe wrote:
Hi All,
In my local setup before pool exhaustion exception is thrown, all the
connections seem to be in freezed and when checking processList in mysql,
those connections are in sleep state and doesn't execute any queries. After
waiting for maxWait period the pool exhausted exception gets thrown and
seems to reset the connections and then the queries are getting processed
as normally.
>
So, my question is, with pool exhausted scenarios, doesn't existing
connections execute their queries during that time(maxWait) and try to
resolve the exhausted behaviour by releasing those connections to idle
queue automatically? When checking the JMX matrix during this pool
exhausted time all the connections are in the active queue.
https://blog.christopherschultz.net/2009/03/16/properly-handling-pooled-jdbc-connections/
If not, what i am experiencing is as expected behaviour where the system is
stuck after pool exhaustion for the best case of maxWait?
Most of the time I've seen this kind of behavior it's due to sloppy
resource-management.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
