Original: After using the DBCP connection pool, the access speed has increased by 100-150%, but the experiment shows that if the load pressure reaches more than 10 times more than the actual load, that is, the maximum number of connectors is more than 10 times, the DBCP is unidentified, and It is often not finally recovered. One of the reasons is due to the high load, DBCP returns the connected or outdated connection to the caller, resulting in flow over, so that all IO processes are hanging. The only way is to restart Tomcat. The solution is to check whether the connection is closed before getting the connection, and finally there is a security mechanism to prevent DDoS refusal response. If you can't, you can get a connection from JDBC. Although the response speed of each page is only about three minutes or so, it will not crash after DDOS. It is a rare advantage.
