processing threads to be created by the HTTPConnector.
<Connector port="8080" address="localhost" maxThreads="250" maxHttpHeaderSize="8192" emptySessionPath="true" protocol="HTTP/1.1" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" />
This determines the maximum number of simultaneous requests that can be handled. If not specified, this attribute is set to the default value of 200.
How the process works:
- At server startup, the HTTP Connector will create a number of processing threads based on the value configured for the minSpareThreads attribute.
- Each incoming request requires a thread for the duration of that request.
- If the number of simultaneous requests cannot be handled by the currently available request processing threads, additional threads will be created up to the configured maximum (the value of the maxThreads attribute).
- If still more simultaneous requests are received, they are stacked up up to the configured maximum (the value of the acceptCount attribute).
- Any further simultaneous requests will receive "connection refused" errors, until resources are available to process them.
maxThreads is an important tuning parameter, however if you are reaching an error like:
org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (150) areyou should at first investigate if it's rather a problem of individual requests taking too long: are your threads returning to the pool? if, for example, database connections are not released, threads pile up waiting to obtain a database connection thereby making it impossible to process additional requests. This is a problem in your webapp.
currently busy, waiting. Increase maxThreads (150) or check the servlet status
Take a thread dump to find out where they're stuck. Increasing too much maxThreads will lead to :
- Consume a good chunk of memory.
- Your system will spend too much time context switching