commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Denson" <>
Subject RE: DBCP options
Date Wed, 21 May 2003 20:25:13 GMT

  I haven't gotten to the point you are but it looks like the
setTimeBetweenEvictionRunsMillis() method is what you want.  The docs
say that a non-positive value means that there will be no runs.  So if
it defaults to zero which seems likely then it isn't making eviction

There is also the setMinEvictableIdleTimeMillis() which may be effecting


-----Original Message-----
From: Durham David Contr 805 CSS/SCBE
Sent: Wednesday, May 21, 2003 12:14 PM
To: Jakarta Commons Users List; Matthew Denson
Subject: RE: DBCP options

> -----Original Message-----
> From: Matthew Denson []
> I would recommend using the Jdbc2PoolDataSource which is in
> common-dbcp
> after version 1.0.  The API page for that package
> ons/dbcp/j
> dbc2pool/package-summary.html is very helpful.  If you want other help
> let me know I got something to work that is very similar to your
> situation for Oracle8i.

The help is much appreciated.

My understanding is that using setDefaultMaxActive(int maxActive) will
mean that I will never have more than max connections active.
Furthermore, using setDefaultMaxIdle(int maxIdle) will mean that idle
connections beyond maxIdle will be closed.  When will they be closed?
It doesn't appear idle connections beyond maxIdle are being removed, or
I just don't know what is going to trigger that.  Perhaps I need to do a
bit more config for that to happen?

> Hope this helps,
> Matthew


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message