RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15
Just wondering if anyone has solved this, I have been having the same issue. I basically just need Tomcat to send the 503 message through the JK connector so Apache can handle it instead of Tomcat returning its own 503 message. The intended goal is to have apache display a static maintenance page if the web-app is stopped, instead of tomcat returning its own generated 503 response. Thanks for any info, -Rick -Original Message- From: Yue Mu [mailto:[EMAIL PROTECTED] Posted At: Saturday, February 04, 2006 11:59 PM Posted To: Tomcat Dev Conversation: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15 Subject: RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15 Thanks, Chuck. In my case, the default servlet/container DID send the HTTP 503 error back, displaying the error with the Tomcat default 503 error page, instead of the custom error page. I also did a small experiment by removing the web application all together. In this case, the container returns the custom 404 error page which is correct since the web app is permanently unavailable. So I think Tomcat does the right thing for the most part, with the exception that it fails to pick up the custom error page, unless I missed something with configuration. Thanks, ym Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Yue Mu [mailto:[EMAIL PROTECTED] Subject: RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15 If the sendError method is called on the response, I think the above clause lets the container off the hook, since the app code could not have used the sendError method (since the app was disabled). It would seem a bit risky for the container to be looking at any configuration data or other resources of a disabled app, since that information may well be in a state of flux. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Brings words and photos together (easily) with PhotoMail - it's free and works with Yahoo! Mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15
Thanks, Chuck. In my case, the default servlet/container DID send the HTTP 503 error back, displaying the error with the Tomcat default 503 error page, instead of the custom error page. I also did a small experiment by removing the web application all together. In this case, the container returns the custom 404 error page which is correct since the web app is permanently unavailable. So I think Tomcat does the right thing for the most part, with the exception that it fails to pick up the custom error page, unless I missed something with configuration. Thanks, ym Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Yue Mu [mailto:[EMAIL PROTECTED] Subject: RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15 If the sendError method is called on the response, I think the above clause lets the container off the hook, since the app code could not have used the sendError method (since the app was disabled). It would seem a bit risky for the container to be looking at any configuration data or other resources of a disabled app, since that information may well be in a state of flux. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Brings words and photos together (easily) with PhotoMail - it's free and works with Yahoo! Mail.
RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15
From: Yue Mu [mailto:[EMAIL PROTECTED] Subject: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15 However, when the web application is stopped (unavailable), it returns the default Tomcat 503 error page (see below), not the custom error page. If the application is not available, its custom error pages are also not available. You might be able to put your 503 page in Tomcat's global web.xml, but I can't say that I've tried it. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15
Thanks, Charles. I should have mentioned that I have tried to use the global web.xml but it does not work either. (Just keep the error pages in the same place, and add the error-page's in the global web.xml in $TOMCAT_HOME/conf) According to the spec, it should catch 4xx and 5xx. From Servlet Spec v2.4, SRV.9.9.2 Error Pages == If the sendError method is called on the response, the container consults the list of error page declarations for the Web application that use the status-code syntax and attempts a match. If there is a match, the container returns the resource as indicated by the location entry. ... The default servlet and container will use the sendError method to send 4xx and 5xx status responses, so that the error mechanism may be invoked. Thanks, YM Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Yue Mu [mailto:[EMAIL PROTECTED] Subject: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15 However, when the web application is stopped (unavailable), it returns the default Tomcat 503 error page (see below), not the custom error page. If the application is not available, its custom error pages are also not available. You might be able to put your 503 page in Tomcat's global web.xml, but I can't say that I've tried it. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Relax. Yahoo! Mail virus scanning helps detect nasty viruses!
RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15
From: Yue Mu [mailto:[EMAIL PROTECTED] Subject: RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15 If the sendError method is called on the response, I think the above clause lets the container off the hook, since the app code could not have used the sendError method (since the app was disabled). It would seem a bit risky for the container to be looking at any configuration data or other resources of a disabled app, since that information may well be in a state of flux. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
