Yes, but the way that the default, non-APR, AJP/1.3 Connector works, connections generally will stay open tying up the corresponding threads. This means that acceptCount doesn't really do very much in this case. Tomcat will end up failing the request if it can't find a free thread for it.
The APR and (experimental) NIO AJP/1.3 Connectors don't have this problem, since they don't have any link between the number of threads (which are only for active requests) and number of Socket connections. "Caldarale, Charles R" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > From: Berglas, Anthony [mailto:[EMAIL PROTECTED] > Subject: Effect of MaxThreads > > Tomcat connectors provide maxThreads parameter to throttle > the number of concurrent transactions. But what actually > happens when this number is exceeded? It's in the doc: http://tomcat.apache.org/tomcat-6.0-doc/config/http.html "acceptCount - The maximum queue length for incoming connection requests when all possible request processing threads are in use. Any requests received when the queue is full will be refused. The default value is 10." > We have Apache in front of Tomcat (for dubious reasons). So why not remove the httpd overhead? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
