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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
