This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
On OpenVMS, we often have at least 2 people running NetBeans on the same machine at the same time. The users who are not the first to start NetBeans always get at least one exception while binding a socket for the HTTP server. I assume the same thing would happen on any system where more than one copy of NetBeans was running concurrently. It seems to loop, looking for a socket port that is free, starting at 8082...can the "address already in use exception" be silently ignored? I have reproduced this on other platforms (well, W2K) by just starting multiple copies of NetBeans. Meg Here's the exception: java.net.BindException: address already in use at java.net.PlainSocketImpl.socketBind at java.net.PlainSocketImpl.bind (PlainSocketImpl.java:397) (pc 3) at java.net.ServerSocket.<init>(int,int,java.net.InetAddress) (ServerSocket.java:170) (pc 79) at java.net.ServerSocket.<init>(int,int) (ServerSocket.java:121) (pc 4) at org.apache.tomcat.net.DefaultServerSocketFactory.createSocket(int,int ) (DefaultServerSocketFactory.java:97) (pc 6) at org.apache.tomcat.service.PoolTcpEndpoint.startEndpoint (PoolTcpEndpoint.java:239) (pc 41) at org.apache.tomcat.service.PoolTcpConnector.start (PoolTcpConnector.java:188) (pc 281) at org.apache.tomcat.core.ContextManager.start (ContextManager.java:527) (pc 17) at org.netbeans.modules.httpserver.HttpServerModule$1.run (HttpServerModule.java:106) (pc 10)
I am attaching the patch. With the patch, NetBeans will not display the socket bind exception to the user, but will log it into the ide.log file. Isao Yanagimachi Compaq Computer Corporation
Created attachment 1055 [details] patch for the unnecessary socket bind exception warning to the user
applied to main trunk and nb3.2
Target milestone -> 3.2
*** Issue 8640 has been marked as a duplicate of this issue. ***