Mladen,
Thank you for this excellent information, it sounds like exactly what I
needed- some context for those parameters.
One last question with regards to setting connectionTimeout="xx" in my
server.xml. I'm using tomcat5.0.28- judging by the docs at
http://tomcat.apache.org/tomcat-5.0-d
Kurt Overberg wrote:
It seems that the number of connections
between the apache and the tomcats just start escalating for some
reason. mod_jk.log shows a ton (>50) of these errors:
Hard to tell without httpd.conf and server.xml.
Two things you should know:
1. MaxClients shuld be <= maxThrea
Mladen, thanks for the response. I've been digging into the problem
with netstat a bit. Here is a log of the date, # of connections to
tomcat1, number of connections to tomcat2 (by netstat -a | grep
webserverIP | wc -l). At 10:58 I had to restart the apache because it
was in the "Stuck" stat
Kurt Overberg wrote:
[Tue Apr 04 18:23:35 2006] [info] ajp_process_callback::jk_ajp_common.c
(1384): Connection aborted or network problems
[Tue Apr 04 18:23:35 2006] [info] ajp_service::jk_ajp_common.c (1731):
Receiving from tomcat failed, because of client error without recovery
in send
Gang,
I have a somewhat heavily loaded tomcat application that uses a
fairly standard Apache 1.3.33 / mod_jk 1.2.15 / tomcat 5.0.28 set up. I
am doing load balancing in the mod_jk, going to 2 RedHat 2.6.9 boxes
that run the tomcats. The load is split evenly across the two tomcat
boxes.
