How to we restart a Tomcat 7 instance without redeploying war files

deploymenttomcat7

Scenario: Bad logging configuration internal to war file. No Manager app in the instance.

Is there a JVM property or something we can set that will cause Tomcat to NOT redeploy on restart? That way we can just edit the properties file under webapps. Can't just temporarily move the war file for the startup as this would cause all kinds of organizational auditing problems.

This is a temporary fix, of course. I've been pushing Spring based external configuration for log4j to handle exactly this sort of thing.

Best Answer

Please set the value of the deployOnStartup attribute to false in the Host element (the default is true). Recommend to keep the autoDeploy attribute true in case you will update wars

<Host name="localhost"  deployOnStartup ="false"
            unpackWARs="true" autoDeploy="true" ...>
…
 </Host>

See for details: http://tomcat.apache.org/tomcat-7.0-doc/config/host.html

Related Solutions

Tomcat – Auto-deploy WAR to arbitrary URL on Tomcat

Thanks to a mailing list response, I found a way to do what I want.

The solution is to not use the auto-deploy feature for WAR files in "/var/lib/tomcat6/webapps", but instead uploading the WAR file to another directory. Then one must explicitly create a context configuration file matching the URL path, e.g. "/var/lib/tomcat6/conf/Catalina/localhost/sub#url.xml" with this content:

<Context docBase="/path/to/war/arbitrary-filename.war" />

Tomcat .war deployment and rollback

To be sure, I would undeploy the application, check my tomcat/webapps/ folder for any traces of the application having been left & then deploy the 'original' application.

Best Answer

Related Solutions

Tomcat – Auto-deploy WAR to arbitrary URL on Tomcat

Tomcat .war deployment and rollback

Related Topic