Your error-page declaration only handles errors caused by
sendError(500). It doesn't handle exceptions thrown by the
application. To specify an error page that is called for all unhandled
exceptions, add this:
<error-page>
<exception-type>java.lang.Throwable</exception-type>
<location>/whatever.jsp</location>
</error-page>
--
Len
On 10/1/07, Novaree <[EMAIL PROTECTED]> wrote:
>
> Hi Mark,
>
> The error page is configured, as described in the docs, in the web.xml-file:
>
> <error-page>
> <error-code>500</error-code>
> <location>/jsp/error/500.jsp</location>
> </error-page>
>
> The stack trace is specific to the error caused by the application, ie. it
> is not the same error on each and every occation.
>
> //Casper
>
>
>
> Mark Thomas-15 wrote:
> >
> > Novaree wrote:
> >> Once in a while, when I "accidentally" runs into a code 500 error, I am
> >> presented with the stack trace instead of the (otherwise properly
> >> configured) 500.jsp page. The "correct" code 500 page is display, like, 8
> >> out of 10 times.
> >
> > How is it configured?
> >
> > What does the stack trace look like?
> >
> > Mark
> >
> >
> > ---------------------------------------------------------------------
> > To start a new topic, e-mail: users@tomcat.apache.org
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Unstable-display-of-code-500-pages-tf4546619.html#a12977444
> Sent from the Tomcat - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
