river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patricia Shanahan <p...@acm.org>
Subject Re: moving classserver port
Date Mon, 22 Nov 2010 20:58:27 GMT
Sim IJskes - QCG wrote:
> Caused by: java.io.IOException: failure to bind to 8080
>     at com.sun.jini.tool.ClassServer.init(ClassServer.java:265)
>     at com.sun.jini.tool.ClassServer.<init>(ClassServer.java:208)
>     ... 12 more
> Caused by: java.net.BindException: Address already in use
>     at java.net.PlainSocketImpl.socketBind(Native Method)
>     at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365)
>     at java.net.ServerSocket.bind(ServerSocket.java:319)
>     at java.net.ServerSocket.bind(ServerSocket.java:277)
>     at com.sun.jini.tool.ClassServer.init(ClassServer.java:263)
> 
> The last QA failed this test, the potential for a port clash is high for 
> port 8080 so i'm moving it to 9080.
> 
> 

Don't the test machines have any facility for finding unused socket
numbers? It would be more convenient to do it that way than any fixed
socket, because it would allow delay in cleaning up after a test failure
leaves a socket in use.

Patricia

Mime
View raw message