With tomcat's built-in database pooling, just adding a validation query to the resource config should be all that's necessary. On each borrow of a connection, the connection is tested and closed if the test fails. Failed connections are replaced with new ones.
--David On 2/24/2011 10:49 AM, János Löbb wrote: > Hi, > > What is the very basic structure of a web application that is connected to a > database through a connection pool, but would not require to restart itself > or restart Tomcat when the database goes down - let say for maintenance ? > > Telling otherwise how to write a webapp that would survive a database > recycling and would not require human interactions to make it work again. > > Thanks ahead, > > János > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
