You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2003/08/20 21:37:13 UTC
DO NOT REPLY [Bug 22598] New: -
minIdle Functionality for DBCP via Patches Posted for commons-pool
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22598>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22598
minIdle Functionality for DBCP via Patches Posted for commons-pool
Summary: minIdle Functionality for DBCP via Patches Posted for
commons-pool
Product: Commons
Version: Nightly Builds
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Dbcp
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: wareing@rewc.com
Here are the required patches to expose the minIdle functionality implemented
in commons-pool (see bug #22597: http://nagoya.apache.org/bugzilla/show_bug.cgi?
id=22597). Currently tested and in use with Tomcat 4.1.24.
What it will do is maintain a minimum level of idle connections in your pool
such that if your database goes down for some reason the same thread used for
evicting stale connections will recreate new connections once the database
comes back up.
Note: You will have to activate the evictor thread initially for this to work.
Simply opening and closing a connection related to the DBCP instance in
question will accomplish this.
Patches for commons-dbcp (nightly build on Aug. 14th, 2003) will be attached.