Java listening on port 8080

Web server failed to start. Port 8080 was already in use.

The spring boot Web server failed to start. Port 8080 was already in use. error occurs because port 8080 is already configured with another application, or port 8080 has not been released yet. The spring boot application is trying to configure port 8080 to start a web server. Since the port can not be used, this error is thrown. The action is Identify and stop the process that’s listening on port 8080 or configure this application to listen on another port.

The Spring boot application uses tomcat as a web server. The default tomcat port is 8080. If any application listens to port 8080 and if you start the spring boot application, this exception is thrown as tomcat can not use port 8080.

Exception

Description: Web server failed to start. Port 8080 was already in use. Action: Identify and stop the process that's listening on port 8080 or configure this application to listen on another port.

Root Cause

Tomcat is running on port 8080. Spring boot application uses tomcat as the default web server. The port 8080 is currently being used by the application and tomcat is trying to listen to port 8080. A different application may be used for port 8080. Or the current application is already running. You ‘re trying to get started again.

Solution 1

You’ve already started and running the spring boot application. Now you’re trying to run the spring boot application again. Stop all the instance or restart your IDE.

You may be running an instance on a terminal or command line, or run as a service. Now you’re trying to get your IDE started again. Check all the applications that can use port 8080 and make sure the application is not started.

Solution 2

Some external applications already use port 8080. Check the running application in the task manager, stop the application that listen to port 8080.

The running application can be identified by the process commands. Identify the process that uses port 8080. Stop the application so that port 8080 is released to the other application to be used. Run the command below in linux to find the application that uses port 8080, and then kill the process if you want to stop it.

Solution 3

Some of the valid applications are running the default port. The application that may be used for other purposes can not be stopped. The other option is to change the default listening port in the application.properties and start the spring boot application again.

application.properties

Источник

Spring Boot – APPLICATION FAILED TO START: Web server failed to start. Port 8080 was already in use.

It can be resolved by following given steps(in accordance with your OS):

1. Open command prompt & Check what processes are running at available ports

netstat -ao | find /i "listening"

We get following kind of output:

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 2428

i.e. Port Numbers and what Process Id they are listening to

2. Stop process running at your port number. (In this case it is 8080 & Process Id is 12704)

Please mention correct PID, otherwise you might end up killing some other important process.

1. Go to Task Manager and kill java(Java(TM) Platform SE binary) process (It will close your IDE, which might not be desired)

1. Open Terminal & Check what process is running at port in error

sudo lsof -i tcp:8080 (Mention port number in error)

netstat -vanp tcp | grep 3000

We get following kind of output (using lsof):

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME name 22758 user 16u IPv4 0x449ce55d62d46bc7 0t0 TCP localhost:hbci (LISTEN) name 22758 user 17u IPv6 0x449ce55d5f4a1a87 0t0 TCP localhost:hbci (LISTEN)

i.e. Process Ids that are running on port.

2. Stop process running at your port number. (In this case it is 8080 & Process Id is 12704)

Please mention correct PID, otherwise you might end up killing some other important process.

It is same as that of MacOS

1. Open Terminal & Check what process is running at port in error

sudo lsof -i tcp:8080 (Mention port number in error)

netstat -vanp tcp | grep 3000

We get following kind of output(using lsof):

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java 23672 sine 238u IPv6 3028222 0t0 TCP localhost:http-alt (LISTEN)

i.e. Process Ids that are running on port.

2. Stop process running at your port number. (In this case it is 8080 & Process Id is 12704)

Please mention correct PID, otherwise you might end up killing some other important process.

Hope this post helps you !

In case you have any better solutions please add your comments 😊

Источник

Java.net.BindException: Address already in use: JVM_Bind:8080 Solution

java.net.BindException: Address already in use: JVM_Bind is a common exception in Java with applications trying to connect on a particular port and some other processes either Java or non Java is already connected on that port. You can get «Address already in use: JVM_Bind» error while doing remote debugging in Java in Eclipse, when Eclipse trying to connect to remote Java application when you are starting tomcat and another instance of tomcat is listening on port 8080 you will get java.net.BindException: Address already in use: JVM_Bind:8080.

In this post we will analyze java.net.BindException and trying to figure out cause of «Address already in use: JVM_Bind» before fixing it. This article is in continuation of my earlier tutorial, How to Solve OutOfMemoryError in Java and How to fix ClassNotFoundException in Java.

How to deal with java.net.BindException: Address already in use: JVM_Bind:8080

1. Address already in use: JVM_Bind:8080

This exception is self-explanatory, its saying that a Java application is trying to connect on port 8080 but that port is already used by some other process and JVM Bind to that particular port, here its 8080, is failed. Now to fix this error you need to find out which process is listening of port 8080, we will how to find a process which is listening on a particular port in both windows and Linux.

Find process which is listening on port 8080 in Windows netstat command is your friend, just use netstat with find command as shown in below example:

Last column is PID of process which is listening on port «8080”, possibly a tomcat web server. You can verify it by looking into task manager and displaying PID as column.

Find process which is listening on port 8080 in Linux

Great thing is that you can use netstat command in Linux and UNIX as well, though with little difference in option it can show you process listening on a particular port, instead of «-o» I normally use «-p» and then use UNIX grep command to select particular process with PID.

How to solve «java.net.BindException: Address already in use»

Now since you have find out offending process you can kill that process and restart yours if killing that process is OK, otherwise change the port your web server is using and you will not get «java.net.BindException: Address already in use» Exception, but if you can not kill that process than you need to change your web-server configuration or eclipse configuration to listen on different port.

In case of tomcat you can change it on connector section of server.xml and in case of eclipse you can see here setting up Eclipse for Java remote debugging.

1. While doing Java remote debugging in Eclipse and when Eclipse tries to connect your remote java application on a particular port and that port is not free.

2. Starting tomcat when earlier instance of tomcat is already running and bonded to 8080 port. It will fail with SEVERE: Error initializing endpoint java.net.BindException: Address already in use: JVM_Bind:8080

3. «Address already in use jvm_bind» could also comes up with other web and application servers like weblogic, glassfish and webshere.

I don’t remember count how many times I have got Address already in use: JVM_Bind ERROR but most of the time it turns out that another instance of same process is running and listening on same port,So watch for it and it can save time for you. Some time this is also called «port already in use JVM_Bind» so don’t confuse Address and port is used interchangeably in different places.

7 comments :

Hello there, I am getting below exception, do you know what causing it :

Caused by: java.rmi.server.ExportException: Port already in use: 23602; nested exception is:
java.net.BindException: Address already in use
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:310)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218)

INFO 2013-07-17 12:26:44,447 [main] com.mulesoft.habitat.agent.AnypointAgentUtils: Anypoint Service Registry Agent is DISABLED. Property anypoint.agent.token is missing or empty.
Exception in thread «Thread-0» java.lang.RuntimeException: Cannot open port 6666
at com.mulesoft.mule.debugger.remote.RemoteDebuggerServer.createServerSocket(RemoteDebuggerServer.java:83)
at com.mulesoft.mule.debugger.remote.RemoteDebuggerServer.run(RemoteDebuggerServer.java:33)
Caused by: java.net.BindException: Address already in use: JVM_Bind
at java.net.DualStackPlainSocketImpl.bind0(Native Method)
at java.net.DualStackPlainSocketImpl.socketBind(Unknown Source)
at java.net.AbstractPlainSocketImpl.bind(Unknown Source)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.bind(Unknown Source)
at java.net.ServerSocket.(Unknown Source)
at java.net.ServerSocket.(Unknown Source)
at com.mulesoft.mule.debugger.remote.RemoteDebuggerServer.createServerSocket(RemoteDebuggerServer.java:81)
. 1 more

Very useful information.Thanks a lot

Hello, I am getting Exception in thread «main» java.net.BindException: Address already in use: JVM_Bind, while running my server. I checked its not running already, but I am still getting this error, does Java keeps the port even after process is killed ?
Exception in thread «main» java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.socketBind(Unknown Source)
at java.net.PlainSocketImpl.bind(Unknown Source

Thanks for the post, that was really helpful.
To kill the port use
Windows
REM find the pid
netstat -a -o -n
taskkill /F /PID
Linux
fuser -k 8080/tcp
or
netstat -anp tcp | grep 8080
kill -9 PID
or
lsof -i tcp:8080
kill -9 PID

@Anonymous, thanks for sharing commands to find the kill a process using a certain port, which is also key to solve this error.

First time it won’t show any error.For the second time executing the same program, you have to close the first one which is running using the same port number.
in eclipse and netBeans IDE you can find the option called close in the right bottom corner.

It worked for me..Hope it will work for you too.

Источник