Do you monitor your tomcat server(s) for memory and CPU use? I'd get some baseline measurements and then incrementally increase your maxKeepAliveRequests value until your problem goes away, all the while making sure you don't have memory or CPU issues.
Brian Clark VP, IS Omeda On Jan 18, 2009, at 2:13 PM, Prakash Nathan1 <mrap...@yahoo.com> wrote: Hello We are planning to define the "maxKeepAliveRequests" attribute in Tomcat server.xml As of now, this attribute is not defined and I believe the default value is 100. What is the preferred value to configure? please advise. Here are the environment details Apache Tomcat/4.1.27 JVM/JDK: 1.4.2_06 Platform: OS Red Hat Enterprise Linux AS release 3 (Taroon Update 5) The reason for the definition of the attribute is because we encounter high socket connection issues and we suspect improper HTTP Keep alive configuration could be the root cause. Please let me know if you need more details. Thanks Prakash -- View this message in context: http://www.nabble.com/%22maxKeepAliveRequests%22-attribute-configuration-tp21532375p21532375.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- 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
