Summary Tomcat on Linux before running is slower when starting, analyzing the log discovery, due to some invalid configuration, such as an error such as the IP of the database. The thread block is caused when starting. After cleaning up some unnecessary Content, it was found to be as slow. And there is a more strange question to appear, Starting org / Apache / Catalina / Startup / Bootstrap ... It takes for a long time (approximately 2 minutes) to continue to run. The latter operation is normal. There is no error in this time without any logging. After changing Tomcat, the problem is still existing after JDK. Finally, I have to push evil to the Linux system, because I am not familiar with Linux, I really don't know where to check. After a few parties, it is desperate after it is invalid. I have to restart the server less than the server. But it is developed and tested above. It is too difficult to restart. Later, when I run some Java programs on Windows, the firewall will have a prompt to allow Java to ask a message. Have you found a little inspiration, I ping 127.0.0.1 is not available! Finally, I found a problem. Since I found a system in the past few days, I had to add a firewall. Only a few addresses can be accessed, and all other Input packs are all dropped. When I saw another machine's default iptables rule, I found out that one is like this: -a input -i lo -j accept. Only I forgot to increase the way. After running iptables -a input -i lo -j acceptpt. Start Tomcat is normal. Finally, there are also Service Iptables Save to save the firewall configuration. Summary: This may be due to the fact that the actual work experience is incorrect.
