java - 频繁请求后台导致服务器无响应一般是什么原因呢

Question

有一个按钮用来向后台请求数据，我已经限制了这个按钮，从发起请求到请求数据接收完之间按钮是不可点击的，但是我后台数据返回是很快的，如果快速频繁的点击它，仍然会导致它不断的向后台请求数据，然后请求无响应了，服务器那边没反应了，服务器无法访问了，看后台日志又一切正常，没有任何错误（日志这块不太熟，不确定是真没错误信息，还是信息没有打出来）。
这里我比较困惑：
为什么浏览器端频繁操作会导致服务器端无响应？

Answer 1

The problem was finally solved. The cause of the problem was that the database access did not add transaction annotations, which resulted in the database access connections not being managed. As a result, the number of connections in the connection pool continued to increase and exceeded, and then the server became unresponsive. Normally, this should report an error. The database connection pool I initially chose was org.apache.commons.dbcp.BasicDataSource. I don’t know why no error was reported, which made me unable to locate the problem; then I checked the connection reset information in the tomcat log. I guess it is related to the number of database connections; then I changed a connection pool org.logicalcobwebs.proxool.ProxoolDataSource, which reported an obvious error. When my database access exceeded a certain number of times, an error was reported directly telling me that the number of connections was exceeded; then I found that the connection The data was not released, and then I discovered that there was no transaction annotation in the code (after adding it, spring should be responsible for the management of the database connection, right?). An annotation solved my problem. . . Gained something

Answer 2

The server’s failure to respond can be divided into the following situations

1: The server is down. The server is inaccessible at this time. The entire server has been down. The detection method is the simplest, just ping just click
2: The service is down. It means that the service you provide the response is down, and there is an internal exception in the system. This service may be a process. Detection is also relatively simple, just visit other services to see if they are available.
3: Network abnormality, just use the first step of detection

Back to your question为什么浏览器端频繁操作会导致服务器端无响应？

This may be due to 1: The service has too complex logic and the processing time is too long. As a result, subsequent requests are blocked and suspended. 2: An internal exception caused the process where the service is located to hang up, so subsequent requests cannot be responded to. PS: You can judge the possible error location through the return status code obtained by the request.

Above