As locked JARs on undeploy is a popular topic, I thought I would share a recent discovery. If you read your log4j configuration file from a JAR, the JAR will end up locked, preventing a clean undeploy.
Full details are here: https://issues.apache.org/bugzilla/show_bug.cgi?id=47465 Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
