You can add a SQL statement to verify the connection after each use (set a validation query and set testOnReturn to true), before each use (set a validation query and set testOnBorrow to true), or between use (set a validation query, a testing period, and testWhileIdle to true), or any combination of these.
I think the latter case--testing when idle--is what you want here. It will periodically use the connection if your app isn't otherwise using it, which will keep the firewall and/or database from timing it out. - Rod <http://radio.weblogs.com/0122027/> On Tue, 24 Jun 2003, Serge Knystautas wrote: > There actually has just been some recent discussion on how to handle > this better. > > For now, you can add a SQL statement to verify the connection after each > use. > > -- > Serge Knystautas > President > Lokitech >> software . strategy . design >> http://www.lokitech.com > p. 301.656.5501 > e. [EMAIL PROTECTED] > > Johannes Lietz wrote: > > > I've got the following problem: > > > > I'm using DBCP from inside Tomcat to connect to a database. Between > > Tomcat and database server is a firewall. > > > > And this firewall is causing problems: when a database connection is > > idle for some time, the firewall will block this connection, and not > > drop the connection. > > > > Therefore DBCP thinks the connection is still open and alive and tries > > to use it. And as the connection is blocked, DBCP will wait eternally > > until something happens. > > > > > > My question: Is there any way to configure DBCP to test connections > > regularly and refresh them if necessary? Or to set a timeout when a > > connection is declared dead and dropped? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
