I've discovered that this problem is related to a 90-minute timeout on our firewall. Tomcat sits outside of the firewall, and Oracle resides inside. Since there's no activity for 90 minutes, it closes the connection. Anyone know of a workaround (+ sample code) for this? I'm assuming a ping of some sort using the database connection pool would work.
Thanks, Matt > -----Original Message----- > From: Ryan Cornia [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 29, 2003 10:03 AM > To: [EMAIL PROTECTED] > Subject: RE: Can the JNDI Connection Pool re-connect after failure? > > > I don't have any timeout settings set. I'm also not using the driver > from Oracle. I'm using a third party driver from inetsoftware.de. If > it's not working in 24 hours, I'll let your know. > > Ryan > > > >>> [EMAIL PROTECTED] 01/29/03 09:43AM >>> > Will it work for 24 hours is the question... ;) If it does, maybe I > should > change to a different Oracle JDBC Driver. Do you have any timeout > limitations set on the connecting user? We do, and I'm wondering if > that's > causing my problems. > > Thanks, > > Matt > > > --------------------------------------------------------------------- > 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]
