which is the port of this project has been occupied by other projects, you cannot use it. There are two methods:
1, in the application. Yml file in a new port
2, force to close the occupied port
forces you to close the occupied port
1, open the computer process of CMP according to port to check the program number netstat ano | findstr searches take up port strong>
2. According to the progress of the program, see the specific program name tasklist | findstr searches process number strong>
3, Mandatory, recursive delete the program and its child process taskkill – f – t – im process name (Java. Exe) strong>
p>
After
execution is complete, you can use this port
Read More:
- The Tomcat connector configured to listen on port 8080 failed to start. The port may already be in u
- filezilla Failed to create listen socket on port 21 for IPv4 solution
- Error running ‘Tomcat 8.5.31’: Unable to open debugger port
- [Solved] Tomcat Failed to Start Error: Server Tomcat v8.5 Server at localhost failed to start
- Through PID (process identification) to find the port (port) occupied applications, to solve the problem of port occupied
- Apache service can’t be started under xampp, reporting port occupancy class error [error] Apache will not start without the configured ports free!
- Error: (serious: a child container failed during start) (server component failed to start so Tomcat is unable)
- Solution to the problem that listen TCP 0.0.0.0:3306: bind: address already in use port is occupied in Linux centos7
- Tomcat — failed to start, flash back
- Tomcat service failed to start
- Server Tomcat v8.0 Server at localhost failed to start.
- An error occurred when starting Tomcat in Eclipse: the sub container failed to start
- Port 4200 is already in use.Use ‘-port’ to specify a different port error Reasons
- tomcat Issues org.apache.catalina.LifecycleException: Failed to start component
- Centos Failed to Modify the port of SSH: error: Bind to port 27615 on 0.0.0.0 failed: Permission denied.
- Server Tomcat v7.0 server at localhost failed to start
- Maven failed to start component [standard engine [Tomcat] when using tomcat7 Maven plugin plug-in run
- When docker starts tomcat, the access port of the container displays 404, and the source server fails to find the representation of the target resource or is unwilling to disclose an existing one
- Vue start error: listen eadrnotavail
- Solution to Tomcat starting error listener start