'8080 port already taken issue when trying to redeploy project from Spring Tool Suite IDE
I have strange thing when I try to modify Spring project inside my Spring Tool Suite. On the first load (deploy) everything is fine, application compiles and runs on localhost:8080
When I change something inside code and try to redeploy it (Run it again - Run As Spring Boot App) I get error message
*************************** APPLICATION FAILED TO START
Description:
The Tomcat connector configured to listen on port 8080 failed to start. The port may already be in use or the connector may be misconfigured.
Action:
Verify the connector's configuration, identify and stop any process that's listening on port 8080, or configure this application to listen on another port.
2016-10-19 00:01:22.615 INFO 10988 --- [ main] ationConfigEmbeddedWebApplicationContext : Closing org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@3023df74: startup date [Wed Oct 19 00:01:19 CEST 2016]; root of context hierarchy 2016-10-19 00:01:22.616 INFO 10988 --- [ main] o.s.j.e.a.AnnotationMBeanExporter : Unregistering JMX-exposed beans on shutdown
If I shutdown process on that port manually everything works fine again, but this can't be right way of redeploying Spring app. Am I doing something wrong here?
I'm using :: Spring Boot :: (v1.4.1.RELEASE)
P.S. I'm aware that I can setup some kind of hot-swap mechanism to have automatic reload of page after I change code, but for now I would like to resolve this issue first.
Thanks for any kind of help or info.
Solution 1:[1]
It sometimes happen even when we stop running processes in IDE with help of Red button , we continue to get same error.
It was resolved with following steps,
Check what processes are running at available ports
netstat -ao |find /i "listening"We get following
TCP 0.0.0.0:7981 machinename:0 LISTENING 2428 TCP 0.0.0.0:7982 machinename:0 LISTENING 2428 TCP 0.0.0.0:8080 machinename:0 LISTENING 12704 TCP 0.0.0.0:8500 machinename:0 LISTENING 2428i.e. Port Numbers and what Process Id they are listening to
Stop process running at your port number(In this case it is 8080 & Process Id is 12704)
Taskkill /F /IM 12704(Note: Mention correct Process Id)
For more information follow these links Link1 and Link2.
My Issue was resolved with this, Hope this helps !
Solution 2:[2]
For Mac users(OS X El Capitan):
You need to kill the port that localhost:8080 is running on.
To do this, you need to do two commands in the terminal :N
sudo lsof -i tcp:8080
kill -15 PID
NB! PID IS A NUMBER PROVIDED BY THE FIRST COMMAND.
The first command gives you the PID for the localhost:8080.
Replace the PID in the second command with the PID that the first command gives you to kill the process running on localhost:8080.
Solution 3:[3]
You have to stop the current process and run your new one. In Eclipse, you can press this button to ReLaunch your application: 
Solution 4:[4]
The reason is one servlet container is already running on port 8080 and you are trying to run another one on port 8080.
Check what processes are running at available ports.
For Windows :
netstat -ao |find /i "listening"
OR
netstat -ano | find "8080"(Note: 8080 is port fail to start)
Now try to reLaunch or stop your application.
- To relaunch: you can press this button
- To stop in windows:
Taskkill /F /IM 6592 Note: Mention correct Process Id
right click on the console and select terminate/disconnect all
- Go to
Task Managerand end Java(tm) platform se binary
Another option is :
Go to application.properties file set server.port=0. This will cause Spring Boot to use a random free port every time it starts.
Solution 5:[5]
In my case, the error occurred as the application was unable to access the keystore for ssl.
Starting the application as root user fixed the issue.
Solution 6:[6]
Create application.properties file under src/main/resources folder and write content as
server.port=8084
Its runs fine.
But every time before run need to stop application first by click on red button upper on the IDE
or try
RightClick on console>click terminate/Disconnect All
Solution 7:[7]
If you got any error on your console by saying, “Embedded servlet container failed to start. Port 8080 was already in use.” Then go to application.properties file and add this property “server.port = 8090”.
Actually the default port for spring boot is 8080, if you have something else on that port, the above error will occur. So we are asking spring boot to run on other port by adding “server.port = 8090” in application.properties file.
Solution 8:[8]
This is a typical startup failure due to the embedded servlet container’s port being in use.
Your embedded tomcat container failed to start because Port 8080 was already in use.
Just Identify and stop the process that's listening on port 8080 or configure (in you application.properties file )this application to listen on another port.
Solution 9:[9]
There are two ways to resolve this issue.Try option 1 first, if it doesn't work try option 2, and your problem is solved.
1) On the top right corner of your console, there is a red button, to stop the spring boot application which is already running on this port just click on the red button to terminate.
2) If the red button is not activated you need to right click on the console and select terminate/disconnect all. Hope this helps.
Bonus tip:- If you want to run your server on a different port of your choice, create a file named application.properties in resource folder of your maven project and write server.port=3000 to run your application on port 3000
Solution 10:[10]
- SOLUTION 1
As a solution ,You can change the default port in application.properties by adding this.
server.port = 8090
- SOLUTION 2
If the above solution is not working use this solution. Here we kill the process which used that port using command prompt.
In my case, Port =8090, PID =22208
1). (This use to find PID)
netstat -ano | findstr :8090
2). (Kill that proccess)
taskkill /PID 22208 /F
Good Luck !
Solution 11:[11]
Am I doing something wrong here?
Yes, you are. One servlet container is already running on port 8080 and you are trying to run another one on port 8080 again.
Either restart the server (If there is button for that in STS) or stop and start it
Solution 12:[12]
On Linux Machine, save the bash script and execute it. If you want to free port 8080, Input 8080 when prompted
echo "Enter port number to be closed :: "
read port
sudo kill $(sudo lsof -t -i:$port)
Solution 13:[13]
Just click red button to stop all services on eclipse than re- run application as Spring Boot Application - This worked for me.
Solution 14:[14]
Open "localhost:8080" on your browser and see what is running on this port.
I did it and I just found Oracle 10g XE running on background, so I went to start->Services and stopped all oracle services. Then I redo mvnw spring-boot:run on IntelliJ and it runs like magic.
Solution 15:[15]
hi creating a simple line in application.properties as SERVER_PORT=8090 solved the issue.
Solution 16:[16]
If you are using linux system, use the below command.
fuser -k some_port_number/tcp - that will kill that process.
Sample:-
fuser -k 8080/tcp
Second Option: Configure the tomcat to use a new port
Solution 17:[17]
In Spring Boot Application (Using Spring Starter Project) We Have Update Port in Server.xml using Tomcat server and Add this port in application.property( insrc/main/resources) the code is server.port=8085
And update Maven Project then run application
Solution 18:[18]
There are some processes left in the background on that port, several reasons can cause this problem, but you can solve easily if you end process which is related to 8080 or Spring.
If you are using Linux there is steps how to end process:
- Open terminal and type command "htop"
- press key F3(it will allow you to search)
- Type "8080" if there was no result on 8080 after that try "spring"
- Then Press F9(KILL) And press "9"(SIGKILL)
this will kill process which is left on 8080 port and let you run application.
Solution 19:[19]
Print the list of running processes and try to find the one that says spring in it. Once you find the appropriate process ID (PID), stop the given process.
ps aux | grep spring
kill -9 INSERT_PID_HERE
After that, try and run the application again. If you killed the correct process your port should be freed up and you can start the server again.
Solution 20:[20]
No Need to manually start an application every time at time of development to implements changes use 'spring-boot-devtool' maven dependency.
Automatic Restart : To use the module you simply need to add it as a dependency in your Maven POM:
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-devtools</artifactId>
</dependency>
When you have the spring-boot-devtools module included, any classpath file changes will automatically trigger an application restart. We do some tricks to try and keep restarts fast, so for many microservice style applications this technique might be good enough.
Solution 21:[21]
Goto Window->Preferences, search for Launching.
Select the "Terminate and Relaunch while launching" option.
Press Apply.
Solution 22:[22]
You can use list open file command and then kill the process like below.
sudo lsof -t -i tcp:8181 | xargs kill -9
or
sudo lsof -i tcp:8181
kill -9 PID
Solution 23:[23]
One simple solution for me that worked was to : - Restart the IDE, since the stop Button was no longer visible.
Solution 24:[24]
One line command for MAC users:
kill `lsof -i -n -P | grep TCP | grep 8080 | tr -s " " "\n" | sed -n 2p`
Solution 25:[25]
If you are facing problem while redeploying, the easiest way would be to not leave port occupied. i.e. close the context of your spring application, so that PORT gets closed alongside.
You can do that in these ways:
//open context.
ConfigurableApplicationContext appContext = SpringApplication.run(Application.class, args);
...
//in the end, close it
appContext.close();
Another way would be, to: open context in try() block
try(ConfigurableApplicationContext appContext =
SpringApplication.run(Application.class, args))
{
// your code here
}
try() will take care of closing the context, therefore the PORT, even if code breaks somewhere, by calling AutoCloseable.
ref: try-with-resources
Solution 26:[26]
first running from CMD :
netstat -aon |find /i "listening" |find "8080"
then get PID number and run following command: let it 199,
taskkill /F /PID 199
Solution 27:[27]
If someone accidentally stumble on this post and his problem is that application is starting two times instead of once and it obviosly fails because port is already in use by first instantion of application. Try add these parameters in yml / properties file.
spring.devtools.restart.quiet-period: 2000
spring.devtools.restart.poll-interval: 3000
https://github.com/spring-projects/spring-boot/issues/25269
Solution 28:[28]
# If you are on windows os (1st way)
open task bar
right click on running JDK binary process
after right click then click on end task
# If you are on windows os (2nd way)
- pres
win+r-> press enter (open windows command permot) 
Taskkill /F /IM <PID>
Solution 29:[29]
YOU CAN CHANGE THE PORT NUMBER ALSO, TRYING THAT METHOD WILL CHANGE THE ERROR OF PORT 8080
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow