commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From commons-...@jakarta.apache.org
Subject [Jakarta Commons Wiki] Updated: DBCP
Date Mon, 24 May 2004 09:49:06 GMT
   Date: 2004-05-24T02:49:06
   Editor: DirkVerbeeck <dirkv@apache.org>
   Wiki: Jakarta Commons Wiki
   Page: DBCP
   URL: http://wiki.apache.org/jakarta-commons/DBCP

   typo

Change Log:

------------------------------------------------------------------------------
@@ -59,7 +59,7 @@
 minimum number of connections are created when the pool instance is created
 ? I thought the setMinIdle() does this, but doesn't look so. 
 
-A: You can setMinIdle() to always have a minium amount of idle connection in the pool. (not
only at the start of the pool but the whole time)
+A: You can setMinIdle() to always have a minimum amount of idle connection in the pool. (not
only at the start of the pool but the whole time)
 The minIdle check is done in the evictor thread so timeBetweenEvictionRunsMillis  has to
be set to a non negative-value. (you can optionally turn off the eviction by setting  numTestsPerEvictionRun
to zero or just set minEvictableIdleTimeMillis very high).
 
 A more simple way to create a number of connections at startup is to use the pool.addObject()
method.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message