Poolman has the ability to check the connection prior to using it, and if the connection isn't valid to create new ones to replace the closed ones.
--mikej -=----- mike jackson [EMAIL PROTECTED] > -----Original Message----- > From: Glenn Nielsen [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, August 27, 2002 5:24 PM > To: Tomcat Users List > Subject: Re: connection pooling on tomcat > > > What connection pool are you using, DBCP? > > Rick Reumann wrote: > > I have connection pooling set up on Tomcat. In my server.xml file I > > have added to the ResourceParams: > > > > <parameter> > > <name>validationQuery</name> > > <value>SELECT 'CRAP' FROM DUAL</value> > > </parameter> > > > > The connection pooling seems to work fine, UNLESS the connections are > > manually killed (which are DBA ends up doing each morning for some > > reason when she comes ..just because she hates some of us:). When the > > connections are killed no one is able to do anything because the > > following error comes up: > > > > java.sql.SQLException: ORA-01012: not logged on > > > > Is there some way I can get this pooling to still work even if the > > connections are manually killed? I thought by adding the > > validationQuery param this would fix the problem, but it didn't. > > > > Thanks for any help. > > > > > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
