DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31286>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31286 Memory leaks in JBoss due to LogFactory cache Summary: Memory leaks in JBoss due to LogFactory cache Product: Commons Version: 1.0.4 Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: Logging AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] LogFactory.java maintains a static cache (Hashtable) of LogFactories, keyed by context ClassLoader. In JBoss, and may be in many other J2EE containers, each hot-redeployment of a J2EE application makes a new class loader for the application, destroying all references to the old one. However, commons-logging. jar is loaded by a parent classloader which is common for all applications, and still maintains hard references to would-be-dead ClassLoaders of undeployed applications. This leads to significant memory leaks, because all static members of all classes of the undeployed applications do not become a subject for GC. It would be excellent if this LogFactory caching could be disabled through a config or a WeakHashMap is used instead of Hashtable. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
