Hi
We have the following set of parameters setup for tomcat in our
environment.
maxActive=100
maxWait=60000
maxIdle=15
minIdle=30
initialSize=15
testOnBorrow=false
validationQuery=SELECT 1 FROM DUAL
validationInterval=60000
minEvictableIdleTimeMillis=3000000 ( 3000 secs)
timeBetweenEvictionRunsMillis=300000 (300 secs)
Reading thru the following section, we understood minEvictableIdleTimeMillis
as number of milliseconds a connection has to be idle before it gets removed
from connection pool and timeBetweenEvictionRunsMillis as number of
milliseconds to elapse before running connection validation again. But what we
are noticing is that despite setting timeBetweenEvictionRunsMillis to
300000 (3000 secs or 5 minutes), the test kicks in every 10 minutes and runs
Idle connection validation. We are trying to understand what is triggering the
Idle connection validation every 10 minutes.
https://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html#Common_Attributes
[https://tomcat.apache.org/tomcat-7.0-doc/images/asf-logo.gif]<https://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html#Common_Attributes>
Apache Tomcat 7 (7.0.67) - The Tomcat JDBC Connection
Pool<https://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html#Common_Attributes>
tomcat.apache.org
Introduction: The JDBC Connection Pool org.apache.tomcat.jdbc.pool is a
replacement or an alternative to the Apache Commons DBCP connection pool. So
why do we need a ...
Cheers
Dina
