Causes and solutions for errors caused by Tomcat server startup in eclipse

It took me one afternoon to get it done. It was such a mistake. After an afternoon, I had to share it with you! I hope it will be useful to all of you!
In eclipse, startup of the Tomcat server produces the following errors:

1. Critical: Error initializing endpoint
Java.net. bindexception: address already in use: jvm_bind: 80
At org.apache.tomcat.util.net. pooltcpendpoint. initendpoint (pooltcpendpoint. Java: 258)
At org. Apache. Coyote. http11.http11protocol. INIT (http11protocol. Java: 143)
.................................;
2. Severe: Catalina. Start
Lifecycleexception: protocol handler initialization failed: java.net. bindexception: address already in use: jvm_bind: 80
At org. Apache. Coyote. tomcat5.coyoteconnector. initialize (coyoteconnector. Java: 1404)
At org. Apache. Catalina. Core. standardservice. initialize (standardservice. Java: 605)
.................................;

3. Severe: standardserver. Await: Create [8005]:
Java.net. bindexception: cannot assign requested address: jvm_bind
At java.net. plainsocketimpl. socketbind (native method)
At java.net. plainsocketimpl. BIND (unknown source)
....................................;

The main causes of these errors are:
1. The independent running Tomcat is not closed.

2. tomcat has been run before, or Tomcat is shut down abnormally, and tomcat still exists in the process.

3. The port used by Tomcat is occupied by other software (default Tomcat port: 8080 ).

Solutions to these errors:

1. In the system service, change the Tomcat Startup Mode from "automatic" to "Manual" (by default, Tomcat is a service automatically started with startup ).

2. Disable the independent running tomcat. Make sure that the Tomcat service is disabled before eclipse starts tomcat.

3. Check the task manager to see if there is any tomcat in the process. If yes, turn it off.

4. If you fail to start Tomcat in eclipse, it may be that Tomcat ports are occupied.

A. Find the server. xml file under Tomcat path: .. \ Tomcat 5.0.28 \ conf \, retrieve the port number: 8080, and change it to an unused port number, such as 8088.

B. you can run the "netstat-a" command in DOS to check the port usage and check whether the Tomcat port is occupied by other software (but no software process is occupied here ), to view the ing between the local port and the process, use the tool fport: ([url] http://www.foundstone.com/us/resources/proddesc/fport.htm#/url]) to view the ing between the port and the process, if any process occupies the Tomcat port, you can go to the task manager and turn it off.