Spring Boot application in eclipse, the Tomcat connector configured to listen on port XXXX failed to start

We Are Going To Discuss About Spring Boot application in eclipse, the Tomcat connector configured to listen on port XXXX failed to start. So lets Start this Java Article.

Spring Boot application in eclipse, the Tomcat connector configured to listen on port XXXX failed to start

  1. Spring Boot application in eclipse, the Tomcat connector configured to listen on port XXXX failed to start

    On the console, looking at the topmost right side of the dialog you should see a red button kinda like a buzzer. To stop the spring boot application properly you just ran, go ahead and hit this particular “red” button and your problem is solved. Hope this helps!

  2. Spring Boot application in eclipse, the Tomcat connector configured to listen on port XXXX failed to start

    On the console, looking at the topmost right side of the dialog you should see a red button kinda like a buzzer. To stop the spring boot application properly you just ran, go ahead and hit this particular “red” button and your problem is solved. Hope this helps!

Solution 1

  1. Find the process ID (PID) for the port (e.g.: 8080)

    On Windows:

    netstat -ao | find "8080"
    

    Other Platforms other than windows :

    lsof -i:8080
    
  2. Kill the process ID you found (e.g.: 20712)

    On Windows:

    Taskkill /PID  20712 /F
    

    Other Platforms other than windows :

    kill -9 20712   or kill 20712
    
Advertisements

Original Author sy456 Of This Content

Solution 2

On the console, looking at the topmost right side of the dialog you should see a red button kinda like a buzzer. To stop the spring boot application properly you just ran, go ahead and hit this particular “red” button and your problem is solved. Hope this helps!

Advertisements

Original Author Edge Of This Content

Solution 3

Another easy way of solving this error is right clicking in the console and click on Terminate/Disconnect All. Afterwards run the application it should work fine.

Advertisements

Original Author DvixExtract Of This Content

Solution 4

Issue: It’s because either you are not stopping your application or the application is already somehow running on the same port somehow.

Solution, Before starting it another time, the earlier application needs to be killed and the port needs to be freed up.

Depending on your platform you can run the below commands to stop the application,

on windows

netstat -anp | find “your application port number”` –> find PID

taskkill /F /PID

on Linux,

netstat -ntpl | grep “your application port number”

kill pid // pid you will get from previous command

on Mac OS

lsof -n -iTCP:”port number”

kill pid //pid you will get from previous command

Advertisements

Original Author Amit Of This Content

Conclusion

Advertisements

So This is all About This Tutorial. Hope This Tutorial Helped You. Thank You.

Also Read,

Siddharth

I am an Information Technology Engineer. I have Completed my MCA And I have 4 Year Plus Experience, I am a web developer with knowledge of multiple back-end platforms Like PHP, Node.js, Python and frontend JavaScript frameworks Like Angular, React, and Vue.

Leave a Comment