![]() ![]() If I had to guess, I would suspect that the vast majority of HTTP requests when the server is "choking" is blocked waiting for something to come back from tomcat. Retransmission, the request may be ignored so that retries succeed. Of ECONNREFUSED or, if the underlying protocol supports The queue full the client may receive an error with an indication The backlog parameter defines the maximum length the queue of pendingĬonnections may grow to. When you get 'error 110' trying to connect back into tomcat it indicates you've got a queue of connections waiting to be served that no more can fit into the listening backlog setup for the listening socket in tomcat. I suspect your problem is in tomcat not apache, from the logs you have shown anyway. I would also start looking at even based servers like nginx. i missed out the maxThreads settings for the AJP 1.3 connector. Thansk all for your valuable suggestions. No response has been sent to the client (yet) ajp_get_reply::jk_ajp_common.c (2118): (tom1) Tomcat is down or refused connection. Tomcat is probably not started or is listening on the wrong port (errno=110) ajp_send_request::jk_ajp_common.c (1630): (tom2) connecting to backend failed. SOME ERRORS IN MODJK LOG, I hope this throws some light on the issue. I found around 1000 connections in TIME_WAIT state, no idea what that would mean in terms of performance, i'm sure it must be adding to the problem. I was just monitoring the tcp connections with netstat The server chokes only during peak hours and when there are 300 concurrent requests waiting for the webservice to respond. how to fix this? I'm sure m2xlarge server should serve more requests than 300, probably i might be going wrong with my configuration. I have been trying numerous suggestions but in vain. I have increased the limits of max connection and max clients in both apache and tomcat. following are some configuration i have done which are directly taken from online resources. ![]() I have googled and found numerous suggestions but nothing seems to work. Our application deals with lot of external webservices and we have a very lousy external webservice which takes almost 300 seconds to respond to requests during peak hours.ĭuring peak hours the server chokes at just about 300 httpd processes. We have an apache webserver in front of Tomcat hosted on EC2, instance type is extra large with 34GB memory. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |