Tomcat中acceptCount,maxConnections、maxThreads的含义及关系

阳光穿透心脏的1/2处 2022-05-22 08:46 151阅读 0赞

个人对tomcat连接器3个属性maxConnections、maxThreads、acceptCount的理解：

先摘取官网对这3个属性的描述：

<table>     
 <tbody> 
  <tr> 
   <td>acceptCount</td> 
   <td>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 100.</td> 
  </tr> 
  <tr> 
   <td>maxConnections</td> 
   <td>The maximum number of connections that the server will accept and process at any given time. When this number has been reached, the server will accept, but not process, one further connection. This additional connection be blocked until the number of connections being processed falls below maxConnections at which point the server will start accepting and processing new connections again.<span style="color:#ff0000;"><strong>Note that once the limit has been reached, the operating system may still accept connections based on the acceptCount setting.</strong></span>The default value varies by connector type. For BIO the default is the value of maxThreads unless an Executor is used in which case the default will be the value of maxThreads from the executor. For NIO the default is 10000. For APR/native, the default is 8192.<br>Note that for APR/native on Windows, the configured value will be reduced to the highest multiple of 1024 that is less than or equal to maxConnections. This is done for performance reasons.<br>If set to a value of -1, the maxConnections feature is disabled and connections are not counted.</td> 
  </tr> 
  <tr> 
   <td>maxThreads</td> 
   <td>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. If not specified, this attribute is set to 200. If an executor is associated with this connector, this attribute is ignored as the connector will execute tasks using the executor rather than an internal thread pool. Note that if an executor is configured any value set for this attribute will be recorded correctly but it will be reported (e.g. via JMX) as -1 to make clear that it is not used.</td> 
  </tr> 
 </tbody> 
</table>

其中maxConnections描述红色部分说明当连接数达到最大值后，系统会继续接收连接但不会超过 acceptCount的值。

理解：

我们可以把tomcat比做一个电影院，流程是取号、买票、观影，acceptCount比作前厅(容纳取到号的人)、maxConnections比作大厅（容纳买到票的人）、maxThreads比作影厅（可以理解一个影厅只容纳一个人，因为一个线程同时只处理一个请求），以下场景是针对已达到maxConnections最大值来讨论的

1）取号：如果前厅人数已达到acceptCount，则拿号失败，会得到Connection refused connect的回复信息。反之则会进入前厅，等待买票。

2）买票：当大厅人数小于maxConnections时，前厅的人就可以进入大厅

3）观影：当影厅的人离开时，大厅的部分人能进入影厅，一般来讲大厅的容量要远大于影厅的数量。

本文是针对apache-tomcat-7.0.55做的测试。

tomcat server.xml配置参数

**Servlet的代码：休眠20秒**

protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException \{  
try \{  
InputStream is = request.getInputStream();  
System.out.println(new Date()+":"+is+"开始");  
Thread.sleep(20000);  
System.out.println(new Date()+":"+is+"结束");  
\} catch (InterruptedException e) \{  
// TODO Auto-generated catch block  
e.printStackTrace();  
\}  
\}

一个请求或一个connection的生命周期：可以简单的理解为从doGet或doPost开始response响应结束。

**使用JMeter测试，线程数20，连接超时时间10s，响应超时时间30s**

测试结果：

察看结果数：

第1秒：8个请求得到响应数据：Connection refused connect

第20秒：2个请求正常响应

第30秒：剩余10个请求得到响应数据：Readtimed out

tomcat日志：

打印12组开始结束的日志，说明tomcat会处理acceptCount+maxConnections的请求，说明只要取到号，有足够的耐心，就肯定能够看到电影