I'm having the same issue as documented in:
http://www.nabble.com/httpd-JK-Tomcat-hung-connections-td10403182.html
For our situation, we haven't hit the "server reached MaxClients setting"
issue yet, but we easily could.
We also have this same config running on a Windows cluster and that
envir
I cannot reproduce this error on demand. It happens sporadically throughout
all the logs.
I did remove socket_timeout and set maxThreads to 380 and I'm still seeing
the exact same errors:
[1660:3036] [info] jk_ajp_common.c (840): awaited reply cpong, received 3
instead
[1660:3036] [info] jk_ajp_
With this release, we were adding in some timeouts based on the
recommendations from
http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html
http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html
Previously, our workers.properties looked like:
worker.template-worker.typ
We've been doing some reconfiguration to try to track down some issues and
with one of the changes, we are now getting a number of errors (but not all
the time) like this one:
[8624:1188] [info] jk_ajp_common.c (840): awaited reply cpong, received 3
instead
[8624:1188] [info] jk_ajp_common.c (123
Tomcat 5.5.25
mod_jk 1.2.25
--
View this message in context:
http://www.nabble.com/AJP-connector-question-tp16587397p16592150.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail:
It's an (un)documented attribute called "packetSize" for the AJP connector:
https://issues.apache.org/bugzilla/show_bug.cgi?id=44541
The packetSize attribute is only good for 5.5.20+ and 6.0.2+.
However, I'm having issues with this myself. I've set my max_packet_size in
the worker and the packe
