On Tue, 10 Dec 2002, Martin van Dijken wrote:
> > > > BasicDataSource currently doesn't expose testWhileIdle,
> > > > although if you look at how the other props are dealt with,
> > > > it wouldn't be difficult to expose it (a small change to
> > > > BasicDataSourceFactory and BasicDataSource is
On Mon, 9 Dec 2002, Martin van Dijken wrote:
> > > As for testing for stale connections - there is a parameter when DBCP
> > > pools are created that allow you to specify a query to check a
> > > connections health. If the query fails - then the connection is
> > > considered bad and DBCP will di
> > As for testing for stale connections - there is a parameter when DBCP
> > pools are created that allow you to specify a query to check a
> > connections health. If the query fails - then the connection is
> > considered bad and DBCP will discard the connection and open a new one.
> Right, spec
Tim Funk wrote:
DBCP can close connections if they have been opened to long by a client.
The close check is issued only when another request to obtain a
connection is made.
As for testing for stale connections - there is a parameter when DBCP
pools are created that allow you to specify a query
On Mon, 9 Dec 2002, Tim Funk wrote:
> DBCP can close connections if they have been opened to long by a client.
This is correct.
> The close check is issued only when another request to obtain a
> connection is made.
This isn't quite correct. In fact, I think these "idle time" checks
only run
DBCP can close connections if they have been opened to long by a client.
The close check is issued only when another request to obtain a
connection is made.
As for testing for stale connections - there is a parameter when DBCP
pools are created that allow you to specify a query to check a
conn
