Raible, Matt wrote:
SOLUTION 1: Change timeout values on your firewall.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.
SOLUTION 2: Create a load-on-startup servlet that will "ping" the database every hour.
Nix.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
