Bug 39883 - using antiResourceLocking in context.xml outside of webapp dir causes app delete on shutdown
using antiResourceLocking in context.xml outside of webapp dir causes app del...
Product: Tomcat 5
Classification: Unclassified
Component: Catalina
All Windows XP
: P2 normal (vote)
: ---
Assigned To: Tomcat Developers Mailing List
Depends on:
  Show dependency tree
Reported: 2006-06-23 15:19 UTC by Jeff Macomber
Modified: 2007-03-25 08:37 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Macomber 2006-06-23 15:19:41 UTC
I have an application installed at c:\speechapps\Application_1

containing a META-INF with context.xml.  In the context.xml I have 
reloadable="false" antiJarLocking="true" and antiResourceLocking="true" 
alongiwth the standard docBase and path.  No other entries are present.  If I 
use the manager interface I can install the application and it works fine.  If 
I then shutdown tomcat gracefully, the application is completely deleted from 
the file system.  The context from the /conf/Catalina/localhost is not 
deleted.  On start of tomcat the application is not loaded (since it has been 
deleted from the file system).  If I use the antiResourceLocking=true in the 
webapps directory it does not delete the application content only when used 
outside of webapps.  

To work around this I removed the antiResourceLocking from the context.xml.  
This seems to resolve the issue for now.  This may be a good addition to the 
docs somewhere.
Comment 1 Yoav Shapira 2007-03-25 08:37:37 UTC
You're right, this should be in the docs somewhere.  I've added a bold-type
warning to the antiResourceLocking configuration documentation.