Rob,

First you need to gather the information about the exception, then send
it to who needs to know. You might want to be proactive and send it to
the support team regardless of what the users want...

One thing to lookout for is that depending on where you exception is
thrown the implicit "exception" variable may not be the one you're
looking for and you have to "unwind" the calling stack to find the root
cause. That's what Tomcat's default error page does. I found it
instructive to study the source of the ErrorReportValve in subversion:
<http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/java/org/apache/ca
talina/valves/ErrorReportValve.java>

Look into the "report" method to see how to use "exception.getCause()"
to get to the root cause.

I hope you find this useful.

Florian


> -----Original Message-----
> From: Serge Fonville [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 03, 2008 4:44 PM
> To: Tomcat Users List
> Subject: Re: Custom Error Messages (5xx and 4xx)
> 
> Hi,
> 
> Look at
> http://java.sun.com/developer/EJTechTips/2003/tt0114.html,
> especially the text
> The string isErrorPage="true" causes the Web container to
> define a new
> implicit variable, "exception", that the JSP page can use
> in scriptlets or
> in custom tags. For example, the error page for the current
> example uses the
> "exception" object to report the name of the class that
> caused the
> exception:
> Basically when at the top of the jsp you specify
> isErrorPage=true, you have
> a variable exception that contains the thrown exception
> 
> Hope this helps
> 
> Regards,
> 
> Serge Fonville
> On Mon, Nov 3, 2008 at 10:31 PM, Rob Mercer
> <[EMAIL PROTECTED]>wrote:
> 
> > Hey all,
> >
> >                I'm trying to setup custom error messages
> in Tomcat
> > 6.0.14. I've got the following entry in web.xml:
> >
> >
> >
> > <!-- Error configuration  -->
> >
> >      <error-page>
> >
> >            <error-code>404</error-code>
> >
> >            <location>/error_pages/404.jsf</location>
> >
> >      </error-page>
> >
> >
> >
> >      <error-page>
> >
> >            <error-code>500</error-code>
> >
> >            <location>/error_pages/500.jsf</location>
> >
> >      </error-page>
> >
> > ....
> >
> >
> >
> > And I've got a much less scary set of pages setup but I
> was wondering if
> > there was a way to get the stack trace and error message
> information to
> > shoot to the support team if the user clicked an "email
> the support team
> > about this error message."  Any ideas on how I'd go about
> that?
> >
> >
> >
> > Additionally, is there a way to setup a 5xx page? Just a
> page that
> > handled all 500 pages? Like a web.xml shorthand?
> >
> >
> >
> >
> >
> > Thanks ahead of time!
> >
> >
> >
> > Rob M
> >
> >


This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly 
prohibited and may be unlawful.  If you have received this communication 
in error, please immediately notify the sender by reply e-mail and destroy 
all copies of the communication and any attachments.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to