See http://jakarta.apache.org/commons/dbcp/configuration.html
(testOnBorrow=true is the default, so you would have to change it to false to remove this behavior.) Tim > -----Original Message----- > From: Propes, Barry L [GCG-NAOT] [mailto:[EMAIL PROTECTED] > Sent: Monday, March 19, 2007 12:44 PM > To: Tomcat Users List > Subject: RE: connection pool > > is testOnBorrow an attribute in the xml config? I haven't seen that in my > version, coincidentally. > > -----Original Message----- > From: Tim Lucia [mailto:[EMAIL PROTECTED] > Sent: Monday, March 19, 2007 11:15 AM > To: 'Tomcat Users List' > Subject: RE: connection pool > > > Do you have a validation query? Is testOnBorrow set to true? Doing both > of > these things will force the pool to really close and really re-open any > connection which fails the validation query. > > Tim > > > > -----Original Message----- > > From: Piwoni, Andre [mailto:[EMAIL PROTECTED] > > Sent: Monday, March 19, 2007 12:04 PM > > To: Tomcat Users List > > Subject: RE: connection pool > > > > I have the same problem. Ideally, there shouldn't be any broken > > connections in the pool. When needed > > connection should be created if database is up and running. This doesn't > > seem to be the case. > > > > -----Original Message----- > > From: Gioia, Michael [mailto:[EMAIL PROTECTED] > > Sent: Monday, March 19, 2007 8:52 AM > > To: users@tomcat.apache.org > > Subject: connection pool > > > > Hi, I'm new to tomcat and have a problem with keeping up the connection > > to the database thru the connection pool. > > > > > > > > Almost every weekend the database gets bumped and the java app that were > > running needs to have tomcat restarted to reconnect to the database thru > > the connection pool. When we come in on Monday tomcat and the database > > are up and running, but the app will not connect to the database. > > > > > > > > Is there a way to reestablish the connection so our users don't have to > > wait until we come in on Monday to restart tomcat? > > > > > > > > Many Thanks, > > > > MG > > > > > > ------------------------------------------------------------------------ > -- > > ---- > > > > This email is confidential and may be legally privileged. > > > > It is intended solely for the addressee. Access to this email by anyone > > else, unless expressly approved by the sender or an authorized addressee, > > is unauthorized. > > > > If you are not the intended recipient, any disclosure, copying, > > distribution or any action omitted or taken in reliance on it, is > > prohibited and may be unlawful. If you believe that you have received > this > > email in error, please contact the sender, delete this e-mail and > destroy > > all copies. > > > > > ========================================================================== > > ==== > > > > > > --------------------------------------------------------------------- > > To start a new topic, e-mail: users@tomcat.apache.org > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
