Did you start tomcat yourself first, and then automatically start it again when eclipse is running? Then the port will definitely be occupied. The solution is not to open tomcat manually
I will answer it again after many months. This is actually a problem caused by improper shutdown of tomcat. The first method is relatively gentle and is to clean the project. The second method is that I have tried it all, and used the command line to forcefully close the pid of tomcat. I only write about the mac system here:
ps -e | grep java
Find out the id of tomcat thread
kill -9 <tomcatID>
The third method is the most violent, just restart the computer = =.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Did you start tomcat yourself first, and then automatically start it again when eclipse is running? Then the port will definitely be occupied. The solution is not to open tomcat manually
I will answer it again after many months. This is actually a problem caused by improper shutdown of tomcat.
The first method is relatively gentle and is to clean the project.
The second method is that I have tried it all, and used the command line to forcefully close the pid of tomcat. I only write about the mac system here:
Find out the id of tomcat thread
The third method is the most violent, just restart the computer = =.