pki-bot
commented
4 years ago Comment from edewata (@edewata) at 2013-09-27 20:56:53
There are several ways to stop/undeploy a web application:
- Suppose Tomcat Manager web application is installed in the instance, the selftest subsystem can call the Tomcat Manager to stop the failing subsystem. See:
Stopping a subsystem using Tomcat Manager doesn't seem to be permanent. The subsystem will start again when Tomcat is restarted, but then it will stop again if the selftest is still failing. After fixing the problem, the subsystem can be restarted via the Tomcat Manager.
- Suppose the subsystem is installed outside the 'webapps' folder, it can be undeployed by removing the context.xml for that subsystem. See:
- http://tomcat.apache.org/tomcat-6.0-doc/config/host.html#Automatic Application Deployment
- http://tomcat.apache.org/tomcat-7.0-doc/config/context.html.
This method seems to be permanent, but it requires direct access to the file system. Redeploying the subsystem requires recreating the context.xml.
This issue was migrated from Pagure Issue #745. Originally filed by edewata (@edewata) on 2013-09-19 18:30:23:
When the Tomcat is started it will run the selftests for each subsystem. Currently if the test fails the engine for the subsystem will not run, but the error will only be shown in the system log, so the admin may not be aware of the failure. Also, the Tomcat server and the web application for that subsystem will continue to run and accept client connections, which can lead to confusions or additional risks.
One solution is to shutdown Tomcat if there's a failure, but this will affect other subsystems running in the same instance.
Another solution is to undeploy the web application of the failing subsystem. This way client will know immediately that the service is unavailable, and other subsystems running on the same instance can still continue to run.