On 23/05/2014 17:59, Mark Eggers wrote: > In general, it's not a good idea to reference a zip file. Post > information inline without comments, and with sensitive information > obscured (not removed - since that can alter the configuration meaning).
+1 Thanks for doing this. <snip/> > <Connector port="9011" > address="10.181.42.52" > redirectPort="443" > enableLookups="false" > protocol="AJP/1.3" > URIEncoding="UTF-8" > tomcatAuthentication="false" > maxPostSize="0" > bufferSize="4096" > maxThreads="250" > scheme="https" > proxyPort="443" > proxyName="test.community.xxxx.com" > secure="true" > maxConnections="245"/> <snip/> > In httpd.conf, you have: > > ServerLimit 1536 > MaxClients 1536 > > This seems to be a bit excessive. That is an understatement. As suspected from the description of the issue the root cause is poor configuration. You have a blocking AJP connector (BIO) with maxThreads of 250. Therefore that connector can support a maximum of 250 connections. You have httpd with MaxClients 1536 and - since AJP uses persistent connections - you have httpd trying to create up to 1536 persistent connections. The first 250 attempts will be fine. Attempt 251 are going to fail. The correct fix is to disable connection reuse or switch to the NIO AJP connector which does not have the 1 thread per connection limitation. You need to read these: http://people.apache.org/~markt/presentations/2012-10-Apache-Tomcat-Reverse-proxies.pdf http://people.apache.org/~markt/presentations/2012-10-Apache-Tomcat-Reverse-proxies-notes-rjung.txt Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
