Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 33711]  -
    Memory leak (classloader) with Log4J and Single Sign On.
Message-Id: <20050330114200.45B6E299@ajax.apache.org>
Date: Wed, 30 Mar 2005 13:42:00 +0200 (CEST)

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=33711>.
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=33711


------- Additional Comments From remm@apache.org  2005-03-30 13:41 -------
To be honest, I am not actually interested in fixing your particular problem. I
was thinking first about the generic problem where references to sessions are
kept for some reason by any component. So the feedback I was most interested in
is: does this fix the reference leak to the classloader ?

The design flaw is then in the SSO reverse map if you want to avoid leaking
skeleton objects. One easy solution might be to change it to a WeakHashMap.

I do not have a good memory profiler to recommend (I don't like any at the moment).

-- 
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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org