tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33368] - swallowOutput causes memory leak
Date Sat, 05 Feb 2005 14:20:03 GMT
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=33368>.
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=33368





------- Additional Comments From rainer.jung@kippdata.de  2005-02-05 15:20 -------
Remy: I did understand, that you prefer some refactoring there. But you weren't
precise about only introducing a ThreadLocal (easy) or also making analysis on
probable recursion. I changed the logs HashTable inside SystemLogHandler to a
ThreadLocal and I'm running a series of tests to see, if the memory leak is
gone. I wil post the small patch (for both SystemLogHandlers) as soon, as the
tests succeed.

I would not very much like to go deeper into the question, if a stack
(supporting recursion) is really necessary. In the jasper case it is not (and so
not in the code), but the case of the filters and valves using
/org/apache/tomcat/util/log/SystemLogHandler.java might be different (and even
different in the various TC versions).

-- 
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


Mime
View raw message