DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6749>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6749 work directory not deleted when Context is removed from Tomcat Summary: work directory not deleted when Context is removed from Tomcat Product: Tomcat 4 Version: 4.0.2 Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When removing a Context through the manager or programmatically through the Deployer interface on a Host, the work directory(ies) corresponding to that application are not deleted. The reason I care about this: bizarre behavior occurs when you remove a context and then add a context with the same contextPath within a running Tomcat instance. For instance, certain pages remain as if they were the original pre-removal context, tag library declarations begin to cause exceptions, etc. These issues cease if you stop and restart the server, indicating to me that Tomcat does something on startup to clear stuff out or reinitialize/create some internal data structures such that the context then works. These things do not happen when removing a Context programmatically, but they should. Clearing the work directory would hopefully resolve these issues. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
