|Summary:||Having a context.xml in conf prevents redeployment on startup|
|Product:||Tomcat 8||Reporter:||Kenneth Gendron <kenneth.gendron>|
|Component:||Catalina||Assignee:||Tomcat Developers Mailing List <dev>|
Description Kenneth Gendron 2016-01-14 20:35:11 UTC
If Tomcat is configured to auto-deploy and deploy-on-startup and a context.xml is in the $CATALINA_BASE/conf/[enginename]/[hostname]/ folder, the server will not redeploy the application if the timestamp has changed on the WAR file. If, after startup, the WAR is deployed with a different timestamp, then the application is redeployed as normal. Is this normal? I was trying to ensure that certain applications get deployed first by having their context.xml files deployed to the conf folder, which works; however, it precludes the use of the on-startup-redeploy feature introduced some time ago. Thanks, Ken
Comment 1 Konstantin Kolinko 2016-01-15 12:44:43 UTC
Please provide a step-by-step recipe to reproduce your issue http://tomcat.apache.org/bugreport.html#How_to_write_a_bug_report Your description is not clear.
Comment 2 Mark Thomas 2016-01-20 21:28:02 UTC
I figured out what the report was about. This has been fixed in 9.0.x for 9.0.0.M2 onwards and in 8.0.x for 8.0.31 onwards. I included a test case that confirms the WAR is expanded if it changes while Tomcat is stopped irrespective of deployOnStartUp or autoDeploy.