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_
Hi Darin,
darinpope schrieb:
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
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
darinpope schrieb:
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]
darinpope wrote:
In all instances of the error, it always says "received 3 instead".
Any idea what could be causing this issue?
Probably the 10 second timeout or is too low.
Regards
--
(TM)
-
To start a new topic, e-mail:
