https://issues.apache.org/bugzilla/show_bug.cgi?id=42366
--- Comment #5 from Tom Lamal <[EMAIL PROTECTED]> 2008-04-05 11:41:15 PST --- Please excuse the many posts. > - mod_jk config (workers.properties, Jk* directives) JK* directives: JkWorkersFile /etc/apache2/workers.properties JkLogFile /var/log/jk.log JkLogLevel error JkOptions +FlushPackets (as noted above, it seems to work without +FlushPackets) workers.properties: worker.list=worker1, worker2 worker.worker2.port=8010 worker.worker2.host=127.0.0.1 worker.worker2.type=ajp13 worker.worker1.port=8009 worker.worker1.host=127.0.0.1 worker.worker1.type=ajp13 (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: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
