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:
>>
https://issues.apache.org/bugzilla/show_bug.cgi?id=47465>>
> 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.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@...
For additional commands, e-mail:
users-help@...
