You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2007/05/09 20:35:03 UTC
DO NOT REPLY [Bug 42366] - Memory leak in newer mod_jk version when connection is abortet by the client
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=42366>.
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=42366
rainer.jung@kippdata.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
------- Additional Comments From rainer.jung@kippdata.de 2007-05-09 11:35 -------
I tried to reproduce, but did not succeed. So please give a couple of info:
- mod_jk config (workers.properties, Jk* directives)
During your test:
- does the number of apache processes go up, or is it stable?
- does the number of backend connections go up, or is it stable?
As I understand your report, neither Apache threads, nor backend connections get
hung, but the apache processes grow in size?
Any chance, you retry with Apache 2.0.59?
Furthermore: Could you please save /proc/PID/maps before, after and a few times
during the test, where PID is the PID of one of the Apache children, that
handles the requests (which one gets the requests could be either logged with %P
in the access log, or you simply look at mod_jk log lines, which contain the pid
as a field. Those files are ASCII and can be attached to this BZ.
For my tests, I used a simple test jsp, of the form:
<%@page session="false"%>
<%
long sleepDuration=0;
String sleepDurationParameter = request.getParameter("dur");
if ( sleepDurationParameter != null && ! sleepDurationParameter.equals("") ) {
sleepDuration=Long.valueOf(sleepDurationParameter).longValue();
}
%>
Parameter: <%= sleepDuration %>
Begin Sleeping ...
<%
Thread.sleep(sleepDuration);
%>
Begin Payload
... (about 20K nonsense characters) ...
The End
Could you retry with that? I called it like .../sl.jsp?dur=3000 with a client,
which had a wait timeout of 1 second, I can force connection aborts and
respective error messages, but get not mem leak.
What info/warn/error/emerg messages does your jk log file show?
--
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org