Re: Clarification on behaviour after pool exhaustion happen in tomcat jdbc pool 9.0.16

2021-08-13 Thread Christopher Schultz
Sampath, On 8/12/21 07:02, Sampath Rajapakshe wrote: Hi Chris, Thanks for the detailed explanation, yes, we tried with abandoned true logs and found an issue with our code base as well. It seems we had a case where a single thread creates a new connection and before closing that connection

Re: Clarification on behaviour after pool exhaustion happen in tomcat jdbc pool 9.0.16

2021-08-12 Thread Sampath Rajapakshe
Hi Chris, Thanks for the detailed explanation, yes, we tried with abandoned true logs and found an issue with our code base as well. It seems we had a case where a single thread creates a new connection and before closing that connection creates a new connection and closes that new connection and

Re: Clarification on behaviour after pool exhaustion happen in tomcat jdbc pool 9.0.16

2021-08-11 Thread Christopher Schultz
Sampath, On 8/9/21 01:45, Sampath Rajapakshe wrote: In our case, we know the reason for the pool exhausted behaviour, there are slow queries and also due to high TPS where pool is not enough. So we are expected to get pool exhaustion with current configurations. Ok. What we wanted to verify

Re: Clarification on behaviour after pool exhaustion happen in tomcat jdbc pool 9.0.16

2021-08-08 Thread Sampath Rajapakshe
Hi Chris, Thanks for the clarification. I've gone through the blog, In our case, we know the reason for the pool exhausted behaviour, there are slow queries and also due to high TPS where pool is not enough. So we are expected to get pool exhaustion with current configurations. What we wanted to

Re: Clarification on behaviour after pool exhaustion happen in tomcat jdbc pool 9.0.16

2021-08-06 Thread Christopher Schultz
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