DO NOT REPLY [Bug 33368] - swallowOutput causes memory leak

[bu...@apache.org]

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-04 18:59 -------
I did some parallel work this week and found the same result for mod_jk and
AJP/13 connector with JDK1.5 hprof. We can see the leak in production too,
because we have a lot of worker thread creation and destruction.

The analysis of Robert is correct. I did a quick fix by adding addThread and
removeThread methods to /org/apache/tomcat/util/log/SystemLogHandler.java and
then registered a ThreadPoolListener in /org/apache/jk/common/ChannelSocket.java
that handles addThread and removeThread. Still need to verify, that the leak is
gone.

IT#s intersting that there is another class
/org/apache/jasper/util/SystemLogHandler.java that is used in a similar way,
but cares better about freeing the thread objects at the end of work.

If you are interested I will produce a patch for the Coyote HTTP connector too,
so you can check, if that would fix the problem.

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