For the record, we are using Tomcat 4.1 and it handles the 500 errors
correctly.  However, we have seen issues when request are passed through
Apache.  Be sure to test against Tomcat directly.



-----Original Message-----
From: David Johnson [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 26, 2005 2:51 PM
To: Struts Users Mailing List
Subject: Fwd: <error-page> not catching errors...

I'm forwarding this to the Tomcat List as well, I'll forward any helpful 
responses for archival purposes.
 Thanks all!

 On 5/26/05, David Johnson <[EMAIL PROTECTED]> wrote: 
> 
> Wow
>  It's insane to me that this cant be done with Tomcat 4.1.31
>  the Struts documents tell you to do exactly what I'm trying.
> http://jakarta.apache.org/tomcat/faq/misc.html#error
>  BAH!!!
> 
>  On 5/26/05, Benedict, Paul C <[EMAIL PROTECTED]> wrote: 
> > 
> > Sorry. Just life then. Upgrade to 5 or use the <exception> block in 
> > web.xml instead to catch the java.lang.Exception. This is the workaround

> > you'll have to do if you don't upgrade. 
> > 
> >  -----Original Message-----
> > *From:* David Johnson [mailto: [EMAIL PROTECTED] 
> > *Sent:* Thursday, May 26, 2005 2:39 PM
> > *To:* Benedict, Paul C
> > *Subject:* Re: <error-page> not catching errors...
> > 
> > yeah. 4.1.28 actually.
> > 
> > On 5/26/05, Benedict, Paul C <[EMAIL PROTECTED] > wrote: 
> > > 
> > > Are you using Tomcat 4?
> > > 
> > >  -----Original Message-----
> > > *From:* David Johnson [mailto: [EMAIL PROTECTED] 
> > > *Sent:* Thursday, May 26, 2005 2:37 PM
> > > *To:* Benedict, Paul C
> > > *Subject:* Re: <error-page> not catching errors...
> > > 
> > > I also caused a java.sql.SQLException which didnt get caught either :(
> > > 
> > > On 5/26/05, Benedict, Paul C <[EMAIL PROTECTED] > wrote: 
> > > > 
> > > > David,
> > > > 
> > > > I think Tomcat 4.x has a bug in which 500 errors are not captured. I

> > > > ran
> > > > into this before. Could be? 
> > > > 
> > > > Thanks,
> > > > Paul
> > > > 
> > > > -----Original Message-----
> > > > From: David Johnson [mailto:[EMAIL PROTECTED]
> > > > Sent: Thursday, May 26, 2005 2:34 PM
> > > > To: Struts Users Mailing List 
> > > > Subject: <error-page> not catching errors...
> > > > 
> > > > 
> > > > Hi all
> > > > I've added the following to my web.xml (thanks for the help)
> > > > 
> > > > <error-page> 
> > > > <error-code>500</error-code>
> > > > <location>/error.jsp</location> 
> > > > </error-page>
> > > > <error-page>
> > > > <error-code>404</error-code>
> > > > <location>/error.jsp</location> 
> > > > </error-page>
> > > > <error-page>
> > > > <error-code>java.lang.Exception </error-code>
> > > > <location>/error.jsp</location>
> > > > </error-page>
> > > > 
> > > > and I've added a global forward I invoke from " error.jsp" which 
> > > > points to my
> > > > 
> > > > tiles def as follows
> > > > 
> > > > <forward name="error" path="/page.error" /> 
> > > > 
> > > > the problem is when I cause an error (like stopping the database 
> > > > then trying 
> > > > 
> > > > to hit it or reloading a page that should cause an error 500), I'm 
> > > > not
> > > > seeing my error page.
> > > > 
> > > > am I forgetting something? 
> > > > 
> > > > 
> > > > --
> > > > -Dave
> > > > [EMAIL PROTECTED]
> > > > 
> > > > 
> > > > 
> > > > 
> > > >
----------------------------------------------------------------------------
--
> > > > Notice: This e-mail message, together with any attachments, contains

> > > > information of Merck & Co., Inc. (One Merck Drive, Whitehouse
Station, New 
> > > > Jersey, USA 08889), and/or its affiliates (which may be known
outside the 
> > > > United States as Merck Frosst, Merck Sharp & Dohme or MSD and in
Japan, as 
> > > > Banyu) that may be confidential, proprietary copyrighted and/or
legally 
> > > > privileged. It is intended solely for the use of the individual or
entity 
> > > > named on this message. If you are not the intended recipient, and
have 
> > > > received this message in error, please notify us immediately by
reply e-mail 
> > > > and then delete it from your system. 
> > > > 
> > > >
----------------------------------------------------------------------------
--
> > > > 
> > > 
> > > 
> > > 
> > > -- 
> > > -Dave
> > > [EMAIL PROTECTED] 
> > > 
> > >  
> > >
----------------------------------------------------------------------------
--
> > > Notice: This e-mail message, together with any attachments, contains 
> > > information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New 
> > > Jersey, USA 08889), and/or its affiliates (which may be known outside
the 
> > > United States as Merck Frosst, Merck Sharp & Dohme or MSD and in
Japan, as 
> > > Banyu) that may be confidential, proprietary copyrighted and/or
legally 
> > > privileged. It is intended solely for the use of the individual or
entity 
> > > named on this message. If you are not the intended recipient, and have

> > > received this message in error, please notify us immediately by reply
e-mail 
> > > and then delete it from your system. 
> > > 
> > >
----------------------------------------------------------------------------
--
> > > 
> > 
> > 
> > 
> > -- 
> > -Dave
> > [EMAIL PROTECTED] 
> > 
> >  
> >
----------------------------------------------------------------------------
--
> > Notice: This e-mail message, together with any attachments, contains 
> > information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New 
> > Jersey, USA 08889), and/or its affiliates (which may be known outside
the 
> > United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan,
as 
> > Banyu) that may be confidential, proprietary copyrighted and/or legally 
> > privileged. It is intended solely for the use of the individual or
entity 
> > named on this message. If you are not the intended recipient, and have 
> > received this message in error, please notify us immediately by reply
e-mail 
> > and then delete it from your system. 
> > 
> >
----------------------------------------------------------------------------
--
> > 
> 
> 
> 
> -- 
> -Dave
> [EMAIL PROTECTED] 




-- 
-Dave
[EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to