commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <ma...@apache.org>
Subject Re: DBCP initialSize
Date Mon, 06 Jul 2009 21:55:01 GMT
CrystalCracker wrote:
> I am using dbcp with its default settings inside Grails. When the app boots
> up, I print out the settings as below, which is as per the DBCP docs.
> 
> maxIdle=8
> defaultCatalog=null
> testOnBorrow=false
> logWriter=java.io.PrintWriter@3c4c3922
> defaultTransactionIsolation=-1
> validationQuery=null
> testOnReturn=false
> maxActive=8
> numActive=0
> numTestsPerEvictionRun=3
> minIdle=0
> maxWait=-1
> defaultAutoCommit=true
> connection=org.apache.commons.dbcp.PoolableConnection@27837c8b
> numIdle=0
> testWhileIdle=false
> driverClassName=org.postgresql.Driver
> class=class org.apache.commons.dbcp.BasicDataSource
> accessToUnderlyingConnectionAllowed=false
> removeAbandonedTimeout=300
> defaultReadOnly=false
> logAbandoned=false
> poolPreparedStatements=false
> maxOpenPreparedStatements=-1
> removeAbandoned=false
> minEvictableIdleTimeMillis=1800000
> timeBetweenEvictionRunsMillis=-1
> initialSize=0
> 
> Notice the initialSize is 0 as expected.
> 
> But when I do netstat -na, I see a tcp connection established to the
> database.
> With the initial size 0, and no database calls made yet, I would assume
> there would be no connections to the database as shown by netstat.
> 
> Am I missing anything here?

Driver initialisation maybe?

Mark


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


Mime
View raw message