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=34346>. 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=34346 ------- Additional Comments From [EMAIL PROTECTED] 2005-04-07 17:19 ------- >From your META-INF/context.xml: <Context path="/mmserver" docBase="mmserver" debug="0" reloadable="false" crossContext="false" override="false"> <Logger className="org.apache.catalina.logger.SystemOutLogger" prefix="localhost_mmserver_log." suffix=".txt" timestamp="true" /> </Context> - Logger element does not exist anymore - never use either "path", "docBase", "debug" on your Context element ------- Additional Comments From [EMAIL PROTECTED] 2005-04-07 18:28 ------- Thanks for the useful info for context.xml. Server.xml is untouched, same one as per default Tomcat 5.5.8 installation. Did not provide test war file because did not have any real time to spend on encapsulating the problem. It was sufficient to be aware of the issue and manually deleting the webapp folder after undeployment. Tomcat 5.5.7 did for real undeploy fully the webapp, so it must have been one of the very special cases for which it worked.... Switched to Tomcat 5.5.9, applied the suggested changes to context.xml plus adding the antiJARLocking="true" and antiResourceLocking="true" attributes. Now the webapp fully undeploys itself when using the Tomcat Manager undeploy action (as it did in the past). Case closed I suspect since Tomcat 5.5.8 is probably consigned to history by now. -- 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]
