If you are fronting with Apache, then the mapping between connections and threads is more a function of your MPM. As a result, I'm just going to answer for the stand-alone Connector.
In Tomcat 5.0, there is a one-to-one mapping between socket connections and threads. Pipelined HTTP/1.1 keep-alive connections will all use the same thread to process. In 5.5.10+ this will no longer necessarily be the case. It will be possible for Tomcat to handle many (and the value of 'many' is heavily dependent on what your app does :) more socket connections than the configured maxThreads. "Feng Xie (fxie)" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] I like to get some help on how to configure the maximum number of connections could be supported by Tomcat5.0. There is one config attribute called "maxThreads", according to Tomcat doc, which is " The maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled. ". My question comes from the fact that there might be multiple HTTP requests pipelined in each HTTP/1.1 connections, so can we still treat the "maxThread" as the maxConnections. Thanks in advance, Feng --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
