Hi, You need to configure the connection pool as to how it handles connection. For example, you would want a validation query if the pool supports it (assuming you're using DBCP, it does), and a recycle policy. By default these aren't done because they cost time, and a situation like yours with the network going down periodically is a recipe for other disasters anyways.
Yoav Shapira http://www.yoavshapira.com >-----Original Message----- >From: Alex Korneyev [mailto:[EMAIL PROTECTED] >Sent: Monday, November 22, 2004 12:11 PM >To: Tomcat Users List >Subject: Tomcat 4.1.30 not restoring JDBC connections > >Hello All, > > has anyone ever experienced the following: > > we are using Tomcat's 4.1.30 connection pool. > > For some reason, when network connection goes down, even for 1 sec, > connection pool is not smart enough to either get rid of a connection > and try get another one, or reconnect; > > any ideas? > > Alex K. > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
