Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Date: Thu, 17 Mar 2005 08:34:20 +0100
Message-Id: <200503170734.j2H7YKxW007481@ajax.apache.org>
From: bugzilla@apache.org
To: commons-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 31286]  -
    [logging] Memory leaks in JBoss due to LogFactory cache

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


b_stansberry@hotmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |


------- Additional Comments From b_stansberry@hotmail.com  2005-03-17 08:34 -------
As discussed on the commons-dev list, even using WeakHashtable the classloader
is not released when LogFactoryImpl is loaded by a parent loader and the
Log wrapper is loaded  by a child.  This is because the LogFactoryImpl holds a
reference to the Log in its instances map, and that reference prevents the Log's
classloader being released.

Will attach a patch to the JUnit tests that show the problem.  Sadly, no fix is
in the patch :(

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org