Tomcat startup does not report an error and cannot access the stuck (solved)

Situation description: When
Tomcat was started, no error was reported, and the port monitoring was normal.
The web has been inaccessible, and curl 127.0.0.1:8080 has been stuck without any output, as shown in the following figure:

Using the shutdown.sh script to shut down tomcat will report an error as shown in the figure below:

Reason:
Tomcat called the jdk random number when it was started. The random number is very slow, causing it to get stuck

Solution:
mv /dev/random /dev/random.bak
ln -s /dev/urandom /dev/random

Visit tomcat after running the above two commands, everything is normal