commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dirk Verbeeck <dirk.verbe...@pandora.be>
Subject Re: DBCP - Connection pool --How to close bad connections
Date Fri, 30 Jan 2004 23:27:22 GMT
The parameter you are looking for is "validationQuery" and then enable 
one of the connection validation tests.

This only helps when you are getting SQLExceptions about broken 
connections.

If you run out of connection because they aren't closed everywhere 
then you have to look for the leak.

-- Dirk


raj wrote:

> Hi,
> Thanks for information in advance.
> I am running into an issue where some bad connections
> are hanging not getting closed and eventually going
> away once I restart the server. 
> 
> Problem is some times there are too many effecting
> performance.
> 
> I am closing all the connections in the code.
> I am using poolingDataSource.
> 
> Is there any parameter in DBCP which will determine
> whether an ACTIVE connection is valid or not and then
> if not close the connection without effecting other
> Active connections...
> 
> Some thing like Using For How much time this
> connection is Active..
> 
> Thanks for the help.
> Regards..RAJ




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


Mime
View raw message