[
https://issues.apache.org/jira/browse/LOGGING-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630881#action_12630881
]
Simon Kitching commented on LOGGING-126:
----------------------------------------
Thanks very much for the report and patch; well spotted! I've applied your
patch with a couple of minor modifications.
Could you please test logging trunk (or a nightly build)? If it works for you,
please mark this issue as resolved - or just add a comment.
> Within Tomcat 5.x implementation, under Windows ONLY Commons-logging forbids
> hot deployment due to JAR locking
> ---------------------------------------------------------------------------------------------------------------
>
> Key: LOGGING-126
> URL: https://issues.apache.org/jira/browse/LOGGING-126
> Project: Commons Logging
> Issue Type: Improvement
> Affects Versions: 1.0, 1.0.1, 1.0.3, 1.0.4, 1.1.0, 1.1.1
> Environment: Windows only
> Reporter: Philippe Mouawad
> Attachments: Patch.txt
>
>
> To reproduce the problem:
> Create a WAR that contains a JAR that contains commons-logging.properties.
> Deploy this WAR to TOMCAT 5.x
> Try to redeploy it, it will fail
> This is due to the fact that LogFactory uses url.openStream to open this file
> , thus URLConnection will use an internal cache and this will provoke a lock
> on the file from Window.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
