Wednesday, November 18, 2009 09:58 PM
The best way to handle this would not be in the configuration of Tomcat. Not a good idea to keep a DB connection persistent and un-used for hours. Very bad programming practice.
What one CAN do is find where this exception is generated, CATCH the exception (mmmm that is what exception handling is for) and re-open the connection and try again.