On 23/05/2014 03:42, pradeepgm wrote: > Now we have configured three tomcat instances with below configurations to > test the above issue > > 1. AJP BIO with JkOptions +DisableReuse, connectionTimeout=20000, > maxThreads=250, maxConnection=245 > 2. AJP NIO with maxThreads=250, maxConnection=245, connectionTimeout=20000 > and bufferSize=4096 > 3. Http NIO with maxThreads=250, maxConnection=245, connectionTimeout=20000 > > We have been told that above issue ( tomcat hung and not responding) is due > to AJP
Utter nonsense. It is most likely be due to poor configuration on your part but since you haven't bothered to provide the relevant parts (or indeed any parts) of your httpd configuration no-one here is going to be able to point out the issue(s). > (be it BIO or NIO) connector and if we use http this issue would not > surface. Whether or not switching to HTTP "fixes" the issue is going to depend on what the problem is and how the default settings for AJP and HTTP interact with the problem. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
