I get a similar (but slightly different) message:
[jk_ajp13_worker.c (203)]: connection_tcp_get_message: Error -
jk_tcp_socket_recvfull failed
[jk_ajp13_worker.c (619)]: Error reading request
The differences are likely due to different logging levels; it seems to be
the same error.
I am using Tomcat 3.2.1, Apache 1.3.14. I tried removing the work/*
directories, but that didn't seem to help. I haven't determined yet
whether this error is specific to ajp13, but am researching that now.
The things I am doing that are out of the ordinary are: (1) I'm running
multiple JVMs for multiple virtual hosts, and (2) I'm loading classes from
my own class path instead of the default WEB-INF structure. Could either
of these be affecting things?
This is a pretty serious error -- users see a big ugly error page. I'm
surprised that there's not more discussion of it. Are most other users not
encountering it?
Paul
>I compiled and installed mod_jk and connect with ajp13 to the apache
>server
>(ver. 1.3.11)
>Everything works fine, but when I make a load test the connector
>stops after
>some time
>and prints out the following messages to the mod_jk.log file.
>I changed the jdk version and recompiled the mod_jk module, but with
>no
>success...
>Did anyone had the same problem?
>-andi
>
>[jk_ajp13_worker.c (619)]: Error reading request
>[jk_ajp13_worker.c (203)]: connection_tcp_get_message: Error -
>jk_tcp_socket_recvfull failed
>[jk_connect.c (143)]: jk_open_socket, connect() failed errno = 111
>[jk_ajp13_worker.c (619)]: Error reading request
>[jk_ajp13_worker.c (173)]: In jk_endpoint_t::connect_to_tomcat,
>failed errno
>= 111
