Dan, True enough, except then those queries would get held as a user session, and we don't want that -- which is why we have a 'skinny' health.jsp that checks our app -- and 'should' crash if there are any issues with tomcat or the application -- but in this case, the main pages were getting out of memory exceptions, but the skinny health.jsp was running just fine... which it shouldn't be if there are failures in either Tomcat or the App.
We're using Application Monitor to monitor the app and tomcat JVM instances as well as the health.jsp response. But for the load balancer, which only uses health.jsp, that's what needs to pick up the problem and report accordingly so the load balancer will take that server out of the load balanced cluster. Kim :-) On 8/20/07, Dan Armbrust <[EMAIL PROTECTED]> wrote: > > A simple cron job that points to a URL using lynx, and greps the > output for what it should see will do the trick... > > Dan > > On 8/20/07, Kim Albee <[EMAIL PROTECTED]> wrote: > > Hello -- > > > > We have a load balanced situation, and we have a JSP that runs and > checks > > our application to ensure it's up and returns a string that the monitor > app > > is looking for if all is well. > > > > Repeatedly, that JSP will work, but the site is down because Tomcat hit > an > > OutOfMemory exception -- but our JSP (which is very small) still runs > > through it's process and returns that everything is happy. Our > application > > is up, but the 500 error is an OutOFMemory exception. > > > > We need a fool-proof way of knowing that the site is up or not, > specifically > > so the load balancer will know to stop routing traffic to a server when > it's > > down, and we can have people taking a look at what happened and bring > the > > server back online without loss of service from a user perspective. > > > > Any suggestions on how to accomplish this? > > > > thanks, > > Kim :-) > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
