Bug 34016 - antiResourceLocking webapp fails to deploy on Tomcat restart after Commit Changes in Admin webapp
Summary: antiResourceLocking webapp fails to deploy on Tomcat restart after Commit Cha...
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Webapps:Administration (show other bugs)
Version: 5.5.7
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2005-03-15 13:03 UTC by Ben Spiller
Modified: 2006-06-11 18:04 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Ben Spiller 2005-03-15 13:03:55 UTC
Clicking the Commit Changes option in the Admin webapp resaves all the context
XML files in \conf\ with the current in-memory state. This process does not take
account of the effect of antiResourceLocking (which is turned on in the
META-INF\context.xml file). If a webapp with this option turned on is running
when the Commit Changes button is pressed, the antiResourceLocking-modified
docBase will be written out to disk.

The problem is that should you then stop Tomcat (with the webapp still running),
on startup it will read in the docBase and get very confused because it can't
find the webapp in the \temp\ folder (which of course got deleted on shutdown
cos it was only temporary). Net result is you can't access the webapp and have
to undeploy and redeploy.
Comment 1 Remy Maucherat 2005-03-15 14:06:43 UTC
Never assign a bug directly to someone.
Comment 2 Remy Maucherat 2005-03-15 14:07:05 UTC