我想在 Controller 中测试并行请求。我知道默认情况下，Spring可以处理200个并行请求，我们可以通过修改此属性server.tomcat.max-threads来更改它
我用这个值玩了一点，发现了有趣的事情:
当我启动应用程序时将其设置为3时，我看到正在创建3个线程:http-nio-8080-exec-1,2,3当我将其设置为5时，我会看到5个这样的线程。它继续上升到10，并在10停止。当我将其设置为15时，仍然有10个名称为http-nio-8080-exec的线程。有人可以解释为什么它永远不会超过10吗？
如果我将这样的 Controller
@GetMapping("test")
public String test(@RequestParam("skip") boolean skip) throws InterruptedException {
if(!skip) {
System.out.println("I'm starting waiting");
Thread.sleep(10000);
System.out.println("I stopped waiting");
}
return "dd";
}
同时拥有
server.tomcat.max-threads=200发出10个类似的请求:http://localhost:8080/test?skip=false
并与此同时发出第11个请求:http://localhost:8080/test?skip=true
这些前10个请求应在返回响应之前等待10秒钟，但第11个请求应立即返回-问题是第11个请求也正在等待，因此已被阻止。有人可以解释它是如何工作的吗？如果我将
server.tomcat.max-threads设置为200，那么我希望能够处理200个独立请求，对吗？ 最佳答案
我对此行为感到好奇，并亲自对其进行了测试。不幸的是，我无法确认您的行为。为了能够同时测试对服务的请求，我编写了一个简单的go程序来证明响应时间。因此，我使用您在上面发布的代码以及作为go程序之后的客户端的单一休息终结点启动了Spring Boot服务:
package main
import (
"log"
"os/exec"
"time"
)
func main() {
for i := 0; i< 15; i++ {
go runCmd(i)
}
time.Sleep(time.Second * 50)
}
func runCmd(i int) {
param := "localhost:8080/test?skip=false"
if i > 10 {
param = "localhost:8080/test?skip=true"
}
cmd := exec.Command("curl", param)
log.Printf("Running command %d and waiting for it to finish...", i)
start := time.Now()
err := cmd.Run()
end := time.Now()
duration := end.Sub(start)
log.Printf("Command %d finished within of second %f error: %v", i, duration.Seconds(), err)
}
该程序使用curl来发送前10个带有参数skip = false的请求，以及另外5个带有skip = true的请求。输出为:
2020/03/08 19:21:18 Running command 14 and waiting for it to finish...
2020/03/08 19:21:18 Running command 9 and waiting for it to finish...
2020/03/08 19:21:18 Running command 3 and waiting for it to finish...
2020/03/08 19:21:18 Running command 10 and waiting for it to finish...
2020/03/08 19:21:18 Running command 7 and waiting for it to finish...
2020/03/08 19:21:18 Running command 0 and waiting for it to finish...
2020/03/08 19:21:18 Running command 12 and waiting for it to finish...
2020/03/08 19:21:18 Running command 6 and waiting for it to finish...
2020/03/08 19:21:18 Running command 5 and waiting for it to finish...
2020/03/08 19:21:18 Running command 13 and waiting for it to finish...
2020/03/08 19:21:18 Running command 11 and waiting for it to finish...
2020/03/08 19:21:18 Running command 2 and waiting for it to finish...
2020/03/08 19:21:18 Running command 1 and waiting for it to finish...
2020/03/08 19:21:18 Running command 4 and waiting for it to finish...
2020/03/08 19:21:18 Running command 8 and waiting for it to finish...
2020/03/08 19:21:18 Command 12 finished within of second 0.035109 error: <nil>
2020/03/08 19:21:18 Command 14 finished within of second 0.035290 error: <nil>
2020/03/08 19:21:18 Command 11 finished within of second 0.040090 error: <nil>
2020/03/08 19:21:18 Command 13 finished within of second 0.041358 error: <nil>
2020/03/08 19:21:28 Command 9 finished within of second 10.034510 error: <nil>
2020/03/08 19:21:28 Command 0 finished within of second 10.034436 error: <nil>
2020/03/08 19:21:28 Command 10 finished within of second 10.037470 error: <nil>
2020/03/08 19:21:28 Command 6 finished within of second 10.042294 error: <nil>
2020/03/08 19:21:28 Command 5 finished within of second 10.042328 error: <nil>
2020/03/08 19:21:28 Command 7 finished within of second 10.045510 error: <nil>
2020/03/08 19:21:28 Command 3 finished within of second 10.045638 error: <nil>
2020/03/08 19:21:28 Command 1 finished within of second 10.049024 error: <nil>
2020/03/08 19:21:28 Command 2 finished within of second 10.053824 error: <nil>
2020/03/08 19:21:28 Command 8 finished within of second 10.053102 error: <nil>
2020/03/08 19:21:28 Command 4 finished within of second 10.053306 error: <nil>
正如您在输出请求11-14中看到的那样，该请求没有延迟地完成，因此它们不会被阻塞。因此，您可能必须检查测试，问题可能出在测试中，而不是tomcat配置中。
能够处理200个独立请求的期望是正确的，因此它的行为也应该如此。
关于java - Spring中的并行请求数与http-nio-8080-exec线程数的比较，我们在Stack Overflow上找到一个类似的问题：https://stackoverflow.com/questions/60587217/