-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin,
On 6/7/2011 8:56 AM, Kevin Claver wrote:
> Through further investigation, I now believe the JSF framework I'm
> using is absorbing the error, and the framework's error page is what
> is throwing the 500 error. I wonder if the 500 error thrown
Chris,
Through further investigation, I now believe the JSF framework I'm using is
absorbing the error, and the framework's error page is what is throwing the 500
error. I wonder if the 500 error thrown by the framework's error page should
fall through to the custom error page servlet I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin,
On 6/3/2011 9:43 AM, Kevin Claver wrote:
> When the custom error servlet fails to display, I get the stock tomcat http
> 500 error page.
>
> If I look at the access log, I see the 500 error:
>
> 192.168.xxx.xxx - - [02/Jun/2011:13:53:14 -060
Friday, June 3, 2011 7:47 AM
Subject: RE: error-page for http 500 error code does not work
> From: Kevin Claver [mailto:kcla...@yahoo.com]
> Subject: Re: error-page for http 500 error code does not work
> I zipped the tomcat install and deployed it to my Win 7 machine
> where it works
> From: Kevin Claver [mailto:kcla...@yahoo.com]
> Subject: Re: error-page for http 500 error code does not work
> I zipped the tomcat install and deployed it to my Win 7 machine
> where it works without issue.
I'll hazard a guess that you have a case sensitivity issue.
Thanks for the quick reply!
I zipped the tomcat install and deployed it to my Win 7 machine where it works
without issue.
When the custom error servlet fails to display, I get the stock tomcat http 500
error page.
If I look at the access log, I see the 500 error:
192.168.xxx.xxx - - [02/Jun/2
On 02/06/2011 21:45, Kevin Claver wrote:
> Two things I would like to note:
>
> 1. When I invoke the Java HMAExceptionHandlerServlet configured to be used
> in the error-page block in the application specific web.xml directly from the
> URL in the browser, it works.
>
> 2. Tomcat 5.5.33 does
