Bug 58867 - Having a context.xml in conf prevents redeployment on startup
Having a context.xml in conf prevents redeployment on startup
Product: Tomcat 8
Classification: Unclassified
Component: Catalina
All All
: P2 normal (vote)
: ----
Assigned To: Tomcat Developers Mailing List
Depends on:
  Show dependency tree
Reported: 2016-01-14 20:35 UTC by Kenneth Gendron
Modified: 2016-01-20 21:28 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
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.


Comment 1 Konstantin Kolinko 2016-01-15 12:44:43 UTC
Please provide a step-by-step recipe to reproduce your issue

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.