It might be that there's another process connecting to the same port you're trying to use, try to kill it or change the connection port.


Try changing the port in core-site.xml from 9000 to 9001 as it seems port 9000 doesn't work.


Change the connection port and ip adress. If you're trying to connect to your server from your own computer, check if you haven't already connected to the server in another instance.


You have a different solution? A short tip here would help you and many other users who saw this issue last week.

  • issue with GWT eclipse plugin
    via Stack Overflow by othman
  • Exception in a gwt program
    via Stack Overflow by Sagar Varpe
  • How to connect GWT to Oracle database
    via Stack Overflow by NareN
  • Starting Jetty on port 8888
    via by Zolf,
    • Address already in use: bind at Method) at at at at org.mortbay.jetty.AbstractConnector.doStart( at org.mortbay.jetty.nio.SelectChannelConnector.doStart( at org.mortbay.component.AbstractLifeCycle.start( at org.mortbay.jetty.Server.doStart( at org.mortbay.component.AbstractLifeCycle.start( at org.apache.servicemix.http.jetty.JettyContextManager.createServer( at org.apache.servicemix.http.jetty.JettyContextManager.createContext( at org.apache.servicemix.http.processors.ConsumerProcessor.start( at org.apache.servicemix.soap.SoapEndpoint.activate( at org.apache.servicemix.common.ServiceUnit.start( at org.apache.servicemix.common.BaseServiceUnitManager.start( at org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start( at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start( at org.apache.servicemix.jbi.framework.DeploymentService.start( at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive( at org.apache.servicemix.jbi.framework.AutoDeploymentService$ at at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$ at

    Users with the same issue

    2 times, last one,
    3 times, last one,
    122 times, last one,
    5 times, last one,
    1 times, last one,
    129 more bugmates