On Thu, Aug 20, 2009 at 10:58, Tim Funk<funk...@apache.org> wrote: > From a high level, whats the difference between a webapp thats stopped and a > webapp thats undeployed?
When a webapp is undeployed it is deleted from the webapps directory. When it's stopped it's not deleted and can simply be re-started. In this case it sounds like the OP is doing some maintenance outside of the webapp (database updates, maybe) and just needs to stop the webapp temporarily. > One could call stopped a special scenario. In the past - a 503 was returned > to the user. Now its a 404. IIRC ... it changed to 404 as part of a bug > report but maybe that is the wrong change to make. (Too lazy to look up the > bug report) I don't know about that change, but in the past it wasn't possible to specify a custom error-page for a stopped webapp. (I can't get to my test server today to see if this is still the case.) > [Personally - I'd rather stick apache in front let apache trap the condition > during the outage window and not worry about the rest.] How would you trap the condition? Apache httpd's ErrorDocument directive won't work because as long as Tomcat is running you get Tomcat's error pages. If you stop Tomcat completely then you can use Apache's ErrorDocument to show a "site down" page, but not if you just stop one webapp in Tomcat. -- Len --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
