DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39883>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39883

           Summary: using antiResourceLocking in context.xml outside of
                    webapp dir causes app delete on shutdown
           Product: Tomcat 5
           Version: 5.5.17
          Platform: All
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: [EMAIL PROTECTED]


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.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to