tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yansheng Lin" <>
Subject RE: Problem with custom error pages for Error 500 - Workaround ?
Date Thu, 29 Apr 2004 15:57:55 GMT

I think you are in luck here.  Once you get your tomcat started, it's a fair
game.  For all unhandled requests, i.e., invalid or in your case, specific
webapp hasn't been loaded, tomcat will try to handle it with the default
context.  That would be the place to override the default 500 error page.
But you may want to confirm the load sequence(FAQ is a good place for this),
it would do you no good if Tomcat loads the default last.  I remember there
was a thread on define the load order, you can search the archive.

To define the default context, you set the path attribute to be "".


-----Original Message-----
From: Frank Duffner [] 
Sent: April 29, 2004 09:31
To: Tomcat Users List
Subject: Re: Problem with custom error pages for Error 500 - Workaround ?

>Whatever is defined in your
>deployer(web.xml) is only relevant when you run the web application.  When
>you restart Tomcat, you are effectively shutting down your jsp engine.
that's why I'm not using the contexts web.xml

 > - the web.xml is the one from tomcat not from the context (wouldn't 
make much sense )

>That's why you are getting a 500 when your web server(Apache?) trys to
>connect. Your jsp engine is not serving up anything for the duration of
>You can either come up with a customized page for your web server...
that I already have. but the moment tomcat starts but the webapp isn't 
yet loaded I get the 500 error message from tomcat
and as you said this would be a good way to tell users that the system 
is going to be online soon again, but it seems now the
only way to do so is change the harcoded error page in tomcat :-/


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message