My first inclination is that this a bug or enhancement request.
From a user point of view, if I have an app (which is not the root
webapp) and I stop it, then all requests should then go to the root
webapp. Of course doing this might introduce bad side effects during the
course of an application restart.
As a workaround, there is an option in Tomcat to use your own
ErrorReportValve. This might be an option.
http://tomcat.apache.org/tomcat-6.0-doc/config/host.html - see
errorReportValveClass
-Tim
llg wrote:
Hi,
I have a webapp that needs to be down if we are doing some
maintenance. I use the manager to make the application unavailable but
in this case the 404 customized error-page is not displayed.
I modified the default web.xml (in conf/) to add the error-page 404,
but it doesn't seems to be resolved when the context is stopped.
If I type an URL that doesn't exists, that doesn't map to any context, I
get the right error page. But if it match a context path of a webapp
that is stopped, I have the Tomcat default error page. Is there a way to
fix this?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
