Yes, the current release has only one validation query spot, which as you say is during testOnBorrow.

This will still cause your firewall to kill connections, and then DBCP will validate the connection, find it's bad, and get a good connection for your app. (For me this is preferrable to keeping idle connections open just because of a periodic validation check.)

--
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. [EMAIL PROTECTED]

Johannes Lietz wrote:
Thanks, this is what I'm looking for.

But if I understand the documentation/source correctly these are features of the upcoming 2.0 release? If so I guess this is nothing I would like to use in a production enviroment soon... :-(

Or is setting a validationQuery (which apparently causes some "testOnBorrow") in 1.0 sufficient?


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to