Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts

Friday, April 27, 2018

Windows: java.net.BindException: Address already in use: bind

Issue Details:


Caused by: java.net.BindException: Address already in use: bind

        at sun.nio.ch.Net.bind0(Native Method)

        at sun.nio.ch.Net.bind(Net.java:433)

        at sun.nio.ch.Net.bind(Net.java:425)

        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)

        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)

        at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:210)

        at org.apache.tomcat.util.net.AbstractEndpoint.start(AbstractEndpoint.java:980)

        at org.apache.coyote.AbstractProtocol.start(AbstractProtocol.java:573)

        at org.apache.catalina.connector.Connector.startInternal(Connector.java:993)

        ... 17 common frames omitted

27-04-2018 23:31:20 [o.a.c.h.Http11NioProtocol:179] log : Pausing ProtocolHandler ["http-nio-3000"]

27-04-2018 23:31:20 [o.a.c.c.StandardService:179] log : Stopping service Tomcat

27-04-2018 23:31:20 [o.a.c.u.LifecycleBase:179] log : The stop() method was called on component [StandardServer[-1]] after stop() had already been called. The second call will be ignored.

27-04-2018 23:31:20 [o.a.c.h.Http11NioProtocol:179] log : Stopping ProtocolHandler ["http-nio-3000"]

27-04-2018 23:31:20 [o.a.c.h.Http11NioProtocol:179] log : Destroying ProtocolHandler ["http-nio-3000"]

27-04-2018 23:31:20 [o.s.b.a.l.AutoConfigurationReportLoggingInitializer:101] logAutoConfigurationReport :

Error starting ApplicationContext. To display the auto-configuration report re-run your application with 'debug' enabled.

27-04-2018 23:31:20 [o.s.b.d.LoggingFailureAnalysisReporter:42] report :

***************************

APPLICATION FAILED TO START

***************************

Description:

The Tomcat connector configured to listen on port 3000 failed to start. The port may already be in use or the connector may be misconfigured.

Fixation: 

First, find out which PID is using the port 3000. Then kill the process id.

C:\Users\drakula>netstat -ano | find "3000"

  TCP    0.0.0.0:3000           0.0.0.0:0              LISTENING       8464

  TCP    [::]:3000              [::]:0                 LISTENING       8464

C:\Users\drakula>TASKKILL /PID 8464 /F

SUCCESS: The process with PID 8464 has been terminated.

C:\Users\drakula>

Tuesday, August 16, 2016

Windows Kill Process By Port Number

If you need to kill a process manually on Windows its actually pretty easy. First fire up a command prompt and type the following command.
netstat -a -o -n
To kill the process we need to find the PID of the process in question. I just run down the list by port until I find port 8080 and here you will see the process id was 28344.
Finally with the PID we can run the following command to kill the process
taskkill /F /PID 28344

Specific Port Killing

Open command prompt and run the following commands
 C:\Users\username>netstat -o -n -a | findstr 0.0:3000
   TCP    0.0.0.0:3000      0.0.0.0:0              LISTENING       3116

C:\Users\username>taskkill /F /PID 3116
, here 3116 is the process ID

Reource Link:
  1. Windows Kill Process By Port Number
  2. Kill a Process by Looking up the Port being used by it from a .BAT