org.jboss.netty.channel.ChannelException

Failed to bind to: 0.0.0.0/0.0.0.0:5084

Samebug tips3

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.

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web212

  • via GitHub by Cashe18
    , 10 months ago
    Failed to bind to: 0.0.0.0/0.0.0.0:5084
  • via GitHub by AlexITC
    , 8 months ago
    Failed to bind to: 0.0.0.0/0.0.0.0:8080
  • via incubator-storm-dev by researcher cs, 9 months ago
    Failed to bind to: 0.0.0.0/0.0.0.0:6703
  • Stack trace

    • org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:5084 at org.jboss.netty.bootstrap.ConnectionlessBootstrap.bind(ConnectionlessBootstrap.java:204) at org.traccar.TrackerServer.start(TrackerServer.java:138) at org.traccar.ServerManager.start(ServerManager.java:73) at org.traccar.Main.main(Main.java:33) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:325) at java.lang.Thread.run(Unknown Source) Caused by: java.net.BindException: Address already in use: bind at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.DatagramChannelImpl.bind(Unknown Source) at sun.nio.ch.DatagramSocketAdaptor.bind(Unknown Source) at org.jboss.netty.channel.socket.nio.NioDatagramPipelineSink.bind(NioDatagramPipelineSink.java:129) at org.jboss.netty.channel.socket.nio.NioDatagramPipelineSink.eventSunk(NioDatagramPipelineSink.java:77) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:779) at org.jboss.netty.channel.SimpleChannelHandler.bindRequested(SimpleChannelHandler.java:299) at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:265) at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784) at org.jboss.netty.handler.logging.LoggingHandler.handleDownstream(LoggingHandler.java:338) at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784) at org.jboss.netty.channel.SimpleChannelHandler.bindRequested(SimpleChannelHandler.java:299) at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:265) at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582) at org.jboss.netty.channel.Channels.bind(Channels.java:561) at org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:197) at org.jboss.netty.bootstrap.ConnectionlessBootstrap.bind(ConnectionlessBootstrap.java:198) ... 9 more

    Write tip

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

    Users with the same issue

    Unknown user
    2 times, 1 year ago
    9 times, 13 hours ago
    Once, 2 days ago
    8 times, 5 days ago
    8 times, 1 week ago
    142 more bugmates