Hi, all 3-4 days Tomcat 3.3.1 does not work anymore correctly in conjunction with mod_jk1.2 and shows up follwing lines in the mod_jk.log:
[Tue Nov 25 20:25:10 2003] [jk_ajp13_worker.c (228)]: connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed [Tue Nov 25 20:25:10 2003] [jk_ajp13_worker.c (228)]: connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed [Tue Nov 25 20:25:10 2003] [jk_ajp13_worker.c (712)]: Error reading reply [Tue Nov 25 20:25:10 2003] [jk_ajp13_worker.c (845)]: In jk_endpoint_t::service, get_reply failed in send loop 0 [Tue Nov 25 20:25:10 2003] [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 61 [Tue Nov 25 20:25:10 2003] [jk_ajp13_worker.c (196)]: In jk_endpoint_t::connect_to_tomcat, failed errno = 61 [Tue Nov 25 20:25:10 2003] [jk_ajp13_worker.c (635)]: Error connecting to the Tomcat process. [Tue Nov 25 20:25:10 2003] [jk_ajp13_worker.c (848)]: In jk_endpoint_t::service, send_request failed in send loop 1 [Tue Nov 25 20:25:10 2003] [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 61 [Tue Nov 25 20:25:10 2003] [jk_ajp13_worker.c (196)]: In jk_endpoint_t::connect_to_tomcat, failed errno = 61 [Tue Nov 25 20:25:10 2003] [jk_ajp13_worker.c (635)]: Error connecting to the Tomcat process. [Tue Nov 25 20:25:10 2003] [jk_ajp13_worker.c (848)]: In jk_endpoint_t::service, send_request failed in send loop 2 [Tue Nov 25 20:25:10 2003] [jk_ajp13_worker.c (228)]: connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed [Tue Nov 25 20:25:10 2003] [jk_ajp13_worker.c (712)]: Error reading reply Looking for a solution I found the hint of a few guys that one should increase "maxProcessors" in the server.xml > "MaxClients" in the httpd.conf. At the moment my impression is that "maxProcessors" first was introduced with Tomcat 4.1 and cannot be used under TomCat 3.3.1. So what can I do now? Is there any corresponding variable? Additionally I could read that with ajp13 the support for persistent connections was introduced. But I suggest that this could be the reason for my problems so I wonder how I can disable that? Or can I simply set "KeepAlive" to "off" in the httpd.conf in order to succeed? Best regards Volker --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
