You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Damian Alonso <da...@oopl.com.au> on 2002/06/25 04:53:35 UTC

Tomcat/Mod_JK/Apache Error

Hi All,

I hope someone can help me with this....

I am getting the following errors in my mod_jk.log file:

[jk_connect.c (143)]: jk_open_socket, connect() failed errno = 111
[jk_ajp13_worker.c (196)]: In jk_endpoint_t::connect_to_tomcat, failed errno
= 111
[jk_ajp13_worker.c (635)]: Error connecting to the Tomcat process.
[jk_ajp13_worker.c (848)]: In jk_endpoint_t::service, send_request failed in
send loop 1
[jk_connect.c (143)]: jk_open_socket, connect() failed errno = 111
[jk_ajp13_worker.c (196)]: In jk_endpoint_t::connect_to_tomcat, failed errno
= 111
[jk_ajp13_worker.c (635)]: Error connecting to the Tomcat process.
[jk_ajp13_worker.c (848)]: In jk_endpoint_t::service, send_request failed in
send loop 2
[jk_ajp13_worker.c (228)]: connection_tcp_get_message: Error -
jk_tcp_socket_recvfull failed
[jk_ajp13_worker.c (712)]: Error reading reply
[jk_ajp13_worker.c (845)]: In jk_endpoint_t::service, get_reply failed in
send loop 0
[jk_ajp13_worker.c (381)]: Error ajp13_process_callback - write failed

My configuration is:

Linux O/S
Apache 1.3.20

talking to

Linux O/S
JBoss2.4.4+Tomcat4.0.1 Bundle
using the mod_jk 3.3 web plugin

Problem Description:
We currently have a Servlet/JSP Application deployed onto Tomcat.  We are
finding that for a lot of users, especially during peak times, we are
getting many users that are getting locked out, disconnected, who are losing
their sessions.  We have tried to increase maxProcessors="150" in our
server.xml on the Tomcat side, but that doesn't seem to have helped.  Our
mod_jk.log file is very large, and looks full of erros like the stack trace
above.  I would really appreciate any feedback on this issue, as it has been
very difficult to find a good answers on this issue.

Thanks in advance,

Damian.