Bug 64231 - Tomcat jdbc pool behaviour
Summary: Tomcat jdbc pool behaviour
Status: NEW
Alias: None
Product: Tomcat Modules
Classification: Unclassified
Component: jdbc-pool (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-16 16:24 UTC by leiyu
Modified: 2020-03-16 16:24 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description leiyu 2020-03-16 16:24:44 UTC
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"