https://issues.apache.org/bugzilla/show_bug.cgi?id=47465
Summary: Reading configuration files from a JAR locks the JAR
file
Product: Log4j
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Configurator
AssignedTo: [email protected]
ReportedBy: [email protected]
If a log4j configuration file is found by the classpath search inside a JAR
file, the file will be loaded from the JAR. However, the initial
URLConnection.getDefaultUseCaches() setting means that caching is used and the
JAR file is locked.
This is a particular problem for container environments like Tomcat, as it
prevents a web application from being removed. Whilst the workaround is simple
- don't put your log4j configuration in a JAR - it impacts a large number of
users.
I have a patch and test case for PropertyConfigurator. I still need to test
DOMConfigurator. I will update this bug report with the results of that test
(and a patch if necessary) later today.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
