I don't know about the particular connection pool you are using, but in general I believe the mechanism would be similar to that implemented by Sybase's Jaguar ejb/servlet engine. There a "sanity check" is run on each connection after it has been returned to the pool and before it is re-used. For Sybase it's "select 1 from dummy", for Oracle it could be "Select 1 from dual". If the database had been restarted then the cached connection would fail its sanity check and would be released and replaced by a new connection. I don't know of any other database independent way of doing this.
Best Wishes John Burgess [EMAIL PROTECTED] Tel: 01865 718666 Fax: 01865 718600 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, October 04, 2002 4:38 PM To: tomcat-user Subject: Connection pool DBCP I have been seen that nobody is able to answer to this question, I presume it's interesting for anybody, for a few days. I wish I knew if DBCP is able to find when db is restarted and reconnect. I'd like to use the jakarta instrument DBCP because all the products of the jakarta community are very good, but the main point is to know if DBCP can recconect to DB lonely. Can some answer to this question? Thanks Laura -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.393 / Virus Database: 223 - Release Date: 30/09/02 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.393 / Virus Database: 223 - Release Date: 30/09/02 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
