Umh... I have seen in the past that at times the connection pool believes that the DB is still there even when it is not. I'm not a Tomcat user... at least not yet !
In my case... the infrastructure has a gateway between the application server and the database server. The web application is session based... so the DB errors occur at the log in only and for the first user of the day. So in the case that the DB is not there... the application loops n times until the DB connections that are cached are flushed and new ones are obtained. HTH, Glenn "Scott Purcell" <[EMAIL PROTECTED]> 01/06/2005 10:21 AM Please respond to "Struts Users Mailing List" <user@struts.apache.org> To "Struts Users Mailing List" <user@struts.apache.org> cc Subject RE: Seeking Advice Error Handling I am running Tomcat 5.5, and I am using a roll-your-own database pooling solution. Scott -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 01, 2005 9:18 AM To: Struts Users Mailing List Subject: Re: Seeking Advice Error Handling In what application server is your application running? Do you have any connection pooling? - Glenn "Scott Purcell" <[EMAIL PROTECTED]> 01/06/2005 10:05 AM Please respond to "Struts Users Mailing List" <user@struts.apache.org> To <user@struts.apache.org> cc Subject Seeking Advice Error Handling Hello, I have created a site with a mysql database back-end, and full struts front end. I have a filter to ensure the creation of some session app objects, and the site is pretty clean. But over the weekend, I found a problem that I am seeking advice from. For some reason, the mysql database went down, causing the site to be all screwed up. I have extended the RequestProcessor but can not figure out how to handle errors from the database. I would like to in the requestProcessor extended class, possibly do a simple query against a known table, and if the result is null, switch them to a site down action class. Can this be done in the requestProcessor area? Any advice would be appreciated. Scott --------------------------------------------------------------------- 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]
