Tracy,
The JSP does a call to a method in our app -- which if it runs, that means
the app is up and available -- the method does a simple query against the DB
and then returns a status of OK if the method runs through just fine.
In our example from this weekend -- the health.jsp (which is the one that
does this check) ran and returned a good result, but the main
index.jspreturned the 500 error with the OutOfMemory exception. So
that is what is
confusing here.
thanks,
Kim :-)
On 8/20/07, Nelson, Tracy M. <Tracy.Nelson@nelnet.net> wrote:
>
> How is your JSP checking your application? Are you issuing a request to
> your app and checking the HTTP status? If so, why isn't it recognizing
> the 500? Or is the JSP in your application which is failing?
>
> | -----Original Message-----
> | From: Kim Albee [mailto:mtitania@gmail.com]
> | Sent: Monday, 20 August, 2007 09:48
> |
> | 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.
> -----------------------------------------
> ------------------------------------------------------------
> The information contained in this message is confidential
> proprietary property of Nelnet, Inc. and its affiliated
> companies (Nelnet) and is intended for the recipient only.
> Any reproduction, forwarding, or copying without the express
> permission of Nelnet is strictly prohibited. If you have
> received this communication in error, please notify us
> immediately by replying to this e-mail.
> ------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
|