[LOGGING-51] [logging] Memory leaks in JBoss due to LogFactory cache

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.4
• Fix Version/s: 1.1.0

Environment

Operating System: All
Platform: All

• Bugzilla Id: 31286
• Assignee: Unassigned
• Reporter: Alexey Yudichev
• Created: 18/Sep/04 18:51
• Updated: 29/Dec/09 16:21
• Resolved: 29/Dec/09 16:21

Description

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.