How to avoid java.net.BindException: Address already in use


Answers

I had a similar problem in one of my programs, but it ended up that I was just actually running an instance of the program from my IDE - which I hadn't noticed. Always double check there isn't something running in the background.

Question

The following was running for 1 hour and then closed:

public class Mp extends JWindow implements MouseListener, MouseMotionListener {
    public static Mp j;
  private int serverPort = 0;
  private ServerSocket serverSock = null;
  private Socket sock = null; 

  public static void main(final String[] args) throws IOException, InterruptedException, Exception {
    j = new Mp();
    j.setVisible(true);
    j.waitForConnections();
  }

  public void waitForConnections() {
    while (true) {
      try {
        sock = serverSock.accept();
        System.out.println("[TCPMediaHandler]: Accepted new socket");
        TCPMediaHandler handler = new TCPMediaHandler(sock);
        handler.start();
      } catch (IOException e) {
        e.printStackTrace(System.err);
      }
    }
  }

  public Mp() throws IOException {
    this.serverPort = 38891;
    serverSock = new ServerSocket(serverPort);
    serverSock.setReuseAddress(true);
    //serverSock.setSoTimeout(500);
    //serverSock.setSoLinger(true, 0);
    System.out.println("[TCPMediaHandler]: Server started");      
        this.v1.setBackground(Color.BLACK);
    this.v1.addMouseListener(this);
    /* Close the window */
    this.addWindowListener(new WindowAdapter() {
        public void windowClosing(WindowEvent we) {
          System.exit(0); 
        }
      });
  }

When I re-run the same thing it fails with a java.net.BindException:

$ java -cp /var/tmp/dist/Mp.jar test.Mp
Exception in thread "main" java.net.BindException: Address already in use
    at java.net.PlainSocketImpl.socketBind(Native Method)
    at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:353)
    at java.net.ServerSocket.bind(ServerSocket.java:336)
    at java.net.ServerSocket.<init>(ServerSocket.java:202)
    at java.net.ServerSocket.<init>(ServerSocket.java:114)
    at test.Mp.<init>(Mp.java)
    at test.Mp.main(Mp.java)

It takes about 3 to 4 minutes before it will execute successfully again. How can I make it work immediately after shutting down?

Follow up:

$ netstat | grep 38891
tcp       35      0 localhost:38891         localhost:37842         CLOSE_WAIT 
tcp        0      0 localhost:34955         localhost:38891         ESTABLISHED
tcp       32      0 localhost:38891         localhost:37824         CLOSE_WAIT 
tcp        0      0 localhost:38891         localhost:34955         ESTABLISHED

$ lsof -w -n -i tcp:38891
COMMAND    PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
xdg-scree 5254  sun   29u  IPv4 231948      0t0  TCP *:38891 (LISTEN)
xdg-scree 5355  sun   29u  IPv4 231948      0t0  TCP *:38891 (LISTEN)
xdg-scree 5455  sun   29u  IPv4 231948      0t0  TCP *:38891 (LISTEN)
telnet    7058  sun    3u  IPv4 242987      0t0  TCP 127.0.0.1:34955->127.0.0.1:38891 (ESTABLISHED)
sleep     9002  sun   29u  IPv4 231948      0t0  TCP *:38891 (LISTEN)
sleep     9005  sun   29u  IPv4 231948      0t0  TCP *:38891 (LISTEN)
sleep     9008  sun   29u  IPv4 231948      0t0  TCP *:38891 (LISTEN)



You may have ran this program before and didn't close the socket properly for some reason, so it can still be opened (or another blocking network state), not letting you listen on it again.

Since you are running on Windows, you can check what's using this port (and kill that bastard if it's the case) with TCPView.




You can't share a TCP listening port between two processes even with SO_REUSEADDR.

NB shutdown() does not close a TCP session. It half-closes it. You have to close the socket.





Tags