Re: AJP protocol with Apache Tomcat Version 7.0.52

> 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

Re: AJP protocol with Apache Tomcat Version 7.0.52

Attached all files here. Just masked the customer domain. conf-files.zip Please note that we have multiple tomcat instances supported by one common apache httpd server. I just added the one (Tomcat 7) which is having this issue (serv

Re: AJP protocol with Apache Tomcat Version 7.0.52

Now we have configured three tomcat instances with below configurations to test the above issue 1. AJP BIO with JkOptions +DisableReuse, connectionTimeout=2, maxThreads=250, maxConnection=245 2. AJP NIO with maxThreads=250, maxConnection=245, connectionTimeout=2 and bufferSize=4096 3.

Re: AJP protocol with Apache Tomcat Version 7.0.52

Yes, we have 300 such threads waiting and after some period of time the server is hung and not responding. We are using AJP BIO with below parameters maxThreads=250 maxConnection=245 -- View this message in context: http://tomcat.10.x6.nabble.com/AJP-protocol-with-Apache-Tomcat-Version-7-0-52

Re: AJP protocol with Apache Tomcat Version 7.0.52

> At a quick glance it doesn’t seem like it would be problematic, just reading data. The issue is there are 300 such threads waiting > One way to test this is to disable the pooling (i.e. disablereuse=Off or > JkOptions +DisableReuse). If you disable it and you don’t see any more of > th