https://bz.apache.org/bugzilla/show_bug.cgi?id=64231
Bug ID: 64231
Summary: Tomcat jdbc pool behaviour
Product: Tomcat Modules
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: jdbc-pool
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
If a connection fails and is evicted during testAllIdle(), should something be
replacing it automatically to maintain the min-idle? Our finding is that the
pool drops below min-idle over time and eventually we are seeing connections
needing to be created as load is going up which we desire to avoid (we would
rather connections be created asynchronously to avoid slow response when we
actually need connections). Is this a bug?
We are using Apache Tomcat 9.0.21 and jdbc pool configuration is as follows
factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
initialSize="100"
minIdle="100"
maxIdle="150"
maxActive="200"
maxWait="10000"
maxAge="3600000"
validationQuery="SELECT sysdate FROM dual"
validationQueryTimeout="10000"
testOnBorrow="true"
testWhileIdle="true"
timeBetweenEvictionRunsMillis="600000"
minEvictableIdleTimeMillis="60000"
softMinEvictableIdleTimeMillis="60000"
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
