[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tomcat-user
Subject:    Re: Clarification on behaviour after pool exhaustion happen in tomcat jdbc pool 9.0.16
From:       Christopher Schultz <chris () christopherschultz ! net>
Date:       2021-08-06 22:13:23
Message-ID: d0fd106e-1c4d-5eb5-04b7-c937fc4d0e03 () christopherschultz ! net
[Download RAW message or body]

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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]