-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Windows 2003 Server
I have 2 independent Hudson servers on the same machine, in different folders, using different ports (3128 and 3129), and I want to launch them both. When I launch the first, everything works ok. When I launch the second, after about 1 minute of "Please wait until Hudson initializes" messages, I get this error instead of having it initialized.
I tried starting them alternatively, it's always when the other Hudson is started that this happens.
hudson.util.IOException2: Failed to wait for the Hub launch to complete
at hudson.plugins.selenium.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:103)
at hudson.model.Hudson.(Hudson.java:631)
at hudson.model.Hudson.(Hudson.java:541)
at hudson.WebAppMain$2.run(WebAppMain.java:222)
Caused by: java.util.concurrent.ExecutionException: java.net.BindException: Address already in use: JVM_Bind
at hudson.remoting.Channel$1.adapt(Channel.java:584)
at hudson.remoting.Channel$1.adapt(Channel.java:579)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
at hudson.plugins.selenium.PluginImpl.waitForHubLaunch(PluginImpl.java:106)
at hudson.plugins.selenium.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:101)
... 3 more
Caused by: java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.bind(Unknown Source)
at java.net.ServerSocket.(Unknown Source)
at java.net.ServerSocket.(Unknown Source)
at org.mortbay.jetty.bio.SocketConnector.newServerSocket(SocketConnector.java:78)
at org.mortbay.jetty.bio.SocketConnector.open(SocketConnector.java:72)
at org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:251)
at org.mortbay.jetty.bio.SocketConnector.doStart(SocketConnector.java:145)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at org.mortbay.jetty.Server.doStart(Server.java:239)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at hudson.plugins.selenium.HubLauncher.start(HubLauncher.java:70)
at hudson.plugins.selenium.HubLauncher.call(HubLauncher.java:45)
at hudson.plugins.selenium.HubLauncher.call(HubLauncher.java:25)
at hudson.remoting.UserRequest.perform(UserRequest.java:114)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
It started happening since around build 1.350 (but I don't remember exactly which).