java.net.BindException: The address is not available

[camroe]

I must admit I'm very confused. This is not a new state, just an irritating one.

Anyway, I'm trying to open a ServerSocket on a 9500 using the Personal Profile (no generic connection framework stuff) and in one application (an HTTP Server) I open the socket this way

ServerSocket serverSocket = new ServerSocket(new Integer(System
.getProperty("utils.Httpd.port", "84")).intValue());
try {
while (true) {
Socket socket = serverSocket.accept();
System.out.println("Connection Made from " + socket);
Httpd httpd = new Httpd(socket);
Thread th = new Thread(httpd);
th.start();

} // end while true
} catch (Exception e) {
}
This works great! No problem. I close that application, go to a 2nd app and open the server socket this way.

int serverSocketPort = 1313;
try {
JoinableServicesCache.serverSocket = new ServerSocket(
serverSocketPort);
} catch (IOException e) {
System.out.println("JoinableServicesCache.JoinableServicesCache()");
System.out.println("Error - unable to execute "
+ e.toString());
try {
System.out.println("Addresss:" + InetAddress.getLocalHost());
} catch (UnknownHostException e1) {
System.out.println("Error - UnknownHostException "
+ e1.toString());
System.out.println(serverSocket);

}
e.printStackTrace();
System.exit(-1);
}

This call to open a server socket results in an exception and the output


JoinableServicesCache.JoinableServicesCache()
Error - JMatos unable to execute java.net.BindException: The address is not available
Addresss:localhost/127.0.0.1

I then tried an example out of Elliotte Rusty Harold's "Java Network Programming" and gave more args to the open socket call but to no avail. That call was

ServerSocket httpd = new ServerSocket(1313,10,InetAddress.getByName("192.168.1.112");

This resulted in the same thing. (I know the address because I can ping it).

The only difference that I can see is that one is a local variable and other is a static but I don't think that should make and difference.

Anyone have any ideas of what to try?

Thanks

Cam

[dcrocha]

It looks clear to me that the problem is that the port 1313 is being used by another system service.

Daniel

[camroe]

Yes, good thought. That's what I thought too so I wrote (following an example) a piece of code that listed the 'in use' ports. The result was

======== J9 2.2 Standard Output (Fri Jan 20 09:41:24 2006) ========
There is server on port 4160.
There is server on port 5001.
There is server on port 5003.
Finish List Servers 1 to 10000

both 84 and 1313 were not being used.

I think it has something to do with the way the ServerSocket binds to addresses. The only book I have on it is the O'Reilly "Java Network Programming" and in there it says that both the ServerSocket(int ort) and ServerSocket(int port,int queueLength) constructors "... bind to all local addresses by default". I am guessing that the 9500 has 2 addresses, the 192.168.1.112 address as served by the DHCP server and the localhost/127.0.0.1 address. It appears (to me) that when trying to bind to the 127.0.0.1 address it was raising the exception. To test that out I tried to use the 3rd constructor ServerSocket(int port, int queueLength, InetAddress bindAddress) in a call that looked like

ServerSocket httpd = new ServerSocket(1313,10,InetAddress.getByName("192.168.1.112"));//From the book

but got the same exception. I also changed the port number but again to no avail.

I will continue trying stuff but any suggestions are very welcome!

Cam

The code I used to check the server ports in use is as follows.

public class ListServerPorts {

private static final int FINISH_PORT = 10000;

/**
* @param args
*/
public static void main(String[] args) {
ServerSocket server = null;
for (int port = 1; port <= FINISH_PORT; port++) {
try {
server = new ServerSocket(port);
} catch (IOException ex) {
System.out.println("There is server on port " + port + ".");
} finally {
if (server != null) {
try {
server.close();
} catch (IOException ignore) {
}
} else
server = null;
}
}// end for
System.out.println("Finish List Servers 1 to " + FINISH_PORT);
}
}

[dcrocha]

Let me see if I understood it correctly: if you open a socket on port 84, it works, if you try it on port 1313, it does not, is that right? Actually, in your first post, in the second code snippet, you introduce 2 different things, potentially problematic: 1) a new port 2) JoinableServicesCache usage. Is there any possibility that the problem lies in this JoinableServicesCache class? Like trying to bind twice or so... just wondering.

If you pass a null InetAddress, the system will bind your server socket to all available interfaces, so I don't think you should care about that.

Daniel