https://issues.apache.org/bugzilla/show_bug.cgi?id=52629
Bug #: 52629
Summary: minIdle property behaviour is not the described one
Product: Tomcat Modules
Version: unspecified
Platform: PC
Status: NEW
Severity: normal
Priority: P2
Component: jdbc-pool
AssignedTo: dev@tomcat.apache.org
ReportedBy: guenther.dem...@wuerth-phoenix.com
Classification: Unclassified
Currently (Tomcat JDBC Connection Pool 1.1.0.0) the description of property
midIdle is:
"(int) The minimum number of established connections that should be kept in the
pool at all times ..."
This behaviour is not guaranteed at all times,
it works only in release phases (= when the use is returning more connections
than borrowing) while in growth-phases the pool starves of idle connections.
Example:
If I define the pool with parameters maxActive=300, initialSize=50, minIdle=10
then when the number of active connections reaches 50, the number of idle
connection will be 0 and remain to 0 also after pool-cleaner thread cycle end
and there were no validation queries failing.
If I use indeed c3p0 and define it with parameters maxPoolSize=300,
initialPoolSize=50, minPoolSize=10,
then I have almost always more or less 10 idle connections,
even when the number of active connections reaches 50.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
