Tomcat in eclipse is always in the starting state

Today, I am troubled by a day. In eclipse, it is clear that tomcat has been successfully started, but a starting tomcat process has been starting. When you modify the page and build the workspace, the process remains in the waiting state, and the starting tomcat process has not ended until the set 300-second start time is completed and ended. Of course, tomcat needs to be restarted again at this time.

This creates a vicious circle. Every time you change the page, you have to restart tomcat !!!

 

Various redeployment, various clean, and various restart operations are not fixed. You can see a solution accidentally.

The principle is that I have set the eclipse proxy, but the proxy availability is not very good, or there is a problem, however, when eclipse is started, it determines whether or not tomcat is started to access the tomcat virtual machine through the network, and then accesses it through the proxy. At this time, it is continuously connected, it seems that tomcat has been started all the time. The solution is to cancel using the eclipse proxy. The specific reason remains to be further investigated.

Recently, the company has banned Internet access and launched a browser proxy .... Okay, solved it!