tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: locked JAR files on undeploy - one possible cause
Date Thu, 02 Jul 2009 12:01:05 GMT
André Warnier wrote:
> Mark Thomas wrote:
>> 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:
> Mark,
> is this specifically a log4j-linked problem, or does this affect any
> other properties/configuration files loaded from JARs ?

It will affect any file loaded from a JAR via a URL where there isn't a
call to URLConnection.setUseCaches(false).

Another workaround may be to use a ContextListener and call
URLConnection.setDefaultUseCaches(false) although that may have
performance side effects. One assumes these things are cached for a
reason although I haven't taken the time to look at the source to figure
out what the impact, if any, would be.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message