tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 42366] Memory leak in newer mod_jk version when connection is abortet by the client
Date Sat, 05 Apr 2008 18:41:15 GMT

--- Comment #5 from Tom Lamal <>  2008-04-05 11:41:15 PST ---
Please excuse the many posts.

> - mod_jk config (, Jk* directives)

JK* directives:

   JkWorkersFile /etc/apache2/
   JkLogFile  /var/log/jk.log
   JkLogLevel error
   JkOptions     +FlushPackets

(as noted above, it seems to work without +FlushPackets)
worker.list=worker1, worker2



(worker2 is not in use, there is not even a tomcat responding on that port)

> - does the number of apache processes go up, or is it stable?
it is stable, and the number is the same with both the working and the
problematic version of mod_jk

> - does the number of backend connections go up, or is it stable?
I think it is stable.

the number of client connections, measured with
netstat | grep www | grep ESTA | wc -l
is the same also.

> Any chance, you retry with Apache 2.0.59?
I will try to do that.

> What info/warn/error/emerg messages does your jk log file show?
whenever a connection is dropped by the client, the following error message
appears in the jk.log file (it is the same for version 1.2.6 and 1.2.26:

[jk_ajp_common.c (1462)]: ERROR: Client connection aborted or network problems

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message