That doesn't work for me, I'm afraid. I actually get two different error message codes: If I start up Apache, and try and access the webapp before Tomcat has started, I get WebApp: Error 500. If I've started up and subsequently shut down Tomcat while Apache is running, I get WebApp: Error 404. ErrorDocument doesn't seem to work in either case, at least with mod_webapp. Perhaps I should try mod_jk?
Robert Tansley / Hewlett-Packard Laboratories / +44 (0)117 312 9116 > -----Original Message----- > From: Chad Cannell [mailto:ccannell@;elogex.com] > Sent: 11 November 2002 17:15 > To: Tomcat Users List > Subject: RE: Friendly error messages when Tomcat is down > > > You say you have tried the: ErrorDocument 500 ./systemUnavail.html > directive? We are using this and it works well when Tomacat is down. > > c > > -----Original Message----- > From: Andrew Ormsby [mailto:andrew.ormsby@;lexicle.com] > Sent: Monday, November 11, 2002 11:29 AM > To: [EMAIL PROTECTED] > Subject: Friendly error messages when Tomcat is down > > > Hi, > > Like Robert Tansley in another message on the list earlier > today, we're > trying to get friendly error pages produced when Tomcat is down. > > Specifically, we're using Tomcat 4.1.12 front-ended with > Apache 2.0.43 > via mod_jk2. > > We've tried various combinations of ErrorDocuments in httpd.conf but > these don't seem to have the desired effect. When Tomcat is > unavailable, references to a JSP served by Tomcat produce the > following > page: > > ==== > The servlet container is temporary unavailable or being upgraded > Internal Server Error > > The server encountered an internal error or misconfiguration and was > unable to complete your request. > > Please contact the server administrator, [EMAIL PROTECTED] and inform > them > of the time the error occurred, and anything you might have done that > may > have caused the error. > > More information about this error may be available in the server error > log. > > Additionally, a 500 Internal Server Error error was encountered while > trying to use an ErrorDocument to handle the request. > ==== > > I've seen a reference to a "noWorkerMsg" and "noWorkerCode" in the > documentation for jk2 which look somewhat promising but there's no > explanation of what these do or how to use them. > > Right now, we're stuck. Any suggestions? > > Regards, > > Andy Ormsby > > > -- > To unsubscribe, e-mail: > <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:tomcat-user-help@;jakarta.apache.org> > > > -- > To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
