Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    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.

  2. ,
    Expert tip

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

Solutions on the web

via by Unknown author, 1 year ago
via ignite-user by Yakov Zhdanov, 2 years ago
Address already in use: bind
via by Unknown author, 1 year ago
Address already in use: bind
via GitHub by beckno9
, 1 year ago
Address already in use
via GitHub by HongxuChen
, 2 years ago
Address already in use Address already in use at Method) at at at at at at org.eclipse.jetty.server.AbstractNetworkConnector.doStart( at org.eclipse.jetty.server.ServerConnector.doStart( at org.eclipse.jetty.util.component.AbstractLifeCycle.start( at org.eclipse.jetty.server.Server.doStart( at org.eclipse.jetty.util.component.AbstractLifeCycle.start( at at at at at at org.apache.ignite.internal.IgniteKernal.startProcessor( at org.apache.ignite.internal.IgniteKernal.start( at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0( at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start( at org.apache.ignite.internal.IgnitionEx.start0( at org.apache.ignite.internal.IgnitionEx.start( at org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start( at org.apache.ignite.internal.processors.platform.PlatformIgnition.start([main]