I am also seeing that in Jboss (Back End) that there are lot of keep alive sessions and I think that's the reason I am seeing the timeout. As I add new web server it hits the 250 MaxThreads limit and then it start to timeout. Those threads are there even though not doing any work. I tried disabling keepalive in worker.properties but still those threads are not being freed up.
Could someone please tell me why that might be happening? On Sat, Nov 7, 2009 at 7:25 AM, Mohit Anchlia <mohitanch...@gmail.com> wrote: > To narrow down I just left one node running and started test. When I > look at JkStatus worker I see even though all other nodes are down > it's still showing "OK" in the status. I am not sure why it would do > that. Could this be the reason why I am seeing slow response times in > mod-jk? > > On Fri, Nov 6, 2009 at 6:30 PM, Mohit Anchlia <mohitanch...@gmail.com> wrote: >> I am looking at the tcpdump but I don't see packet retransmits. What >> should I expect to see in tcpdump? thanks for your help. >> >> On Fri, Nov 6, 2009 at 4:05 PM, Rainer Jung <rainer.j...@kippdata.de> wrote: >>> $ grep 110 /usr/include/*/errno.h >>> >>> #define ETIMEDOUT 110 /* Connection timed out */ >>> >>> On 07.11.2009 00:56, Mohit Anchlia wrote: >>>> I turned on mod_jk debug and see: >>> >>>> [Fri Nov 06 15:48:31.190 2009] [31055:4143340384] [info] >>>> ajp_handle_cping_cpong::jk_ajp_common.c (865): timeout in reply cpong >>> >>> So your backend doesn't send the required cpong answer during the >>> timeout ou configured. >>> >>>> [Fri Nov 06 15:48:31.191 2009] [31055:4143340384] [debug] >>>> jk_shutdown_socket::jk_connect.c (680): About to shutdown socket 14 >>>> [Fri Nov 06 15:48:31.256 2009] [31044:4143340384] [debug] >>>> jk_shutdown_socket::jk_connect.c (731): Shutdown socket 14 and read 0 >>>> lingering bytes >>>> [Fri Nov 06 15:48:31.256 2009] [31044:4143340384] [error] >>>> ajp_connect_to_endpoint::jk_ajp_common.c (957): (eitappfe2) >>>> cping/cpong after connecting to the backend server failed (errno=110) >>>> [Fri Nov 06 15:48:31.257 2009] [31044:4143340384] [error] >>>> ajp_send_request::jk_ajp_common.c (1467): (eitappfe2) connecting to >>>> backend failed. Tomcat is probably not started or is listening on the >>>> wrong port (errno=110) >>>> [Fri Nov 06 15:48:31.257 2009] [31044:4143340384] [info] >>>> ajp_service::jk_ajp_common.c (2407): (eitappfe2) sending request to >>>> tomcat failed (recoverable), because of error during request sending >>>> (attempt=1) >>>> [Fri Nov 06 15:48:31.257 2009] [31044:4143340384] [debug] >>>> ajp_service::jk_ajp_common.c (2267): retry 1, sleeping for 100 ms >>>> before retrying >>>> [Fri Nov 06 15:48:31.314 2009] [31032:4143340384] [debug] >>>> jk_shutdown_socket::jk_connect.c (731): Shutdown socket 14 and read 0 >>>> lingering bytes >>>> [Fri Nov 06 15:48:31.315 2009] [31032:4143340384] [error] >>>> ajp_connect_to_endpoint::jk_ajp_common.c (957): (eitappfe2) >>>> cping/cpong after connecting to the backend server failed (errno=110) >>>> [Fri Nov 06 15:48:31.315 2009] [31032:4143340384] [error] >>>> ajp_send_request::jk_ajp_common.c (1467): (eitappfe2) connecting to >>>> backend failed. Tomcat is probably not started or is listening on the >>>> wrong port (errno=110) >>>> >>>> -- >>>> All nodes are up and have plenty of threads configured and free. >>> >>> Yet they are still not responding in time. >>> >>> You can verify using a apcket sniff. >>> >>>> On Fri, Nov 6, 2009 at 3:47 PM, Mohit Anchlia <mohitanch...@gmail.com> >>>> wrote: >>>>> I am continously seeing the following even though all these nodes are >>>>> up and running and receving requests. >>>>> >>>>> [Fri Nov 06 15:43:47.627 2009] [29200:4143332192] [error] >>>>> ajp_send_request::jk_ajp_common.c (1467): (eitappfe3) connecting to >>>>> backend failed. Tomcat is probably not started or is listening on the >>>>> wrong port (errno=110) >>>>> [Fri Nov 06 15:43:47.627 2009] [29200:4143332192] [error] >>>>> ajp_service::jk_ajp_common.c (2426): (eitappfe3) connecting to tomcat >>>>> failed. >>> >>> Regards, >>> >>> Rainer >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >>> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
