tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <ma...@apache.org>
Subject Re: locked JAR files on undeploy - one possible cause
Date Thu, 02 Jul 2009 13:19:52 GMT
André Warnier wrote:
> Mark Thomas wrote:
>> 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).
>>
> To this self-confessed dummy, this sounds as if, even though files
> loaded from JARs may not be so frequent, but given the thousands of
> Tomcat's out there, it ought to affect quite a few installations.

Yep. Hence my e-mail. For the record, I found it looking into an Grails
issue [1].

> Might it also be a reason why some Tomcats do not seem able to shutdown
> properly when told ?

It will only cause an undeploy to fail. It won't interfere with a full
shutdown.

Mark

[1] http://jira.codehaus.org/browse/GRAILS-2544


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message