Tomcat uses 80 ports on the computer.
When the client accesses it, it establishes a connection with the 80 port on the server side.
Now you're doing stress tests. When multiple users visit, the server side of the 80 port will be always connected to occupy, causing the server side of the CPU can easily soar to 100%.
A tomcat connection pool is used to connect to the database.
Probability analysis:
80 is occupied for a long time because Tomcat initiates the connection pool, noting that Tomcat is a connection pool, not a database connection pool,
This connection pool is used to handle the links for outside access to Tomcat, which defaults to 25
You can see it inside the tomcat/conf/server.xml.
As for server-side CPUs, it can easily soar to 100%.
This is
1 Your program running slow, resulting in the use of the CPU, is generally an algorithmic problem
2 Your program has a dead loop.
3 database problems, but generally are design or coding problems
4 hardware is too bad, memory is too small, (may not be small)
5 High load