java.io.IOException

Connection reset by peer

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

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

Solutions on the web5005

  • Connection reset by peer
  • via GitHub by stringpeng
    , 3 months ago
    Connection reset by peer
  • Connection reset by peer
  • Stack trace

    • java.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.write0(Native Method)[na:1.8.0_77] at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)[na:1.8.0_77] at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)[na:1.8.0_77] at sun.nio.ch.IOUtil.write(IOUtil.java:51)[na:1.8.0_77] at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471)[na:1.8.0_77] at org.jboss.netty.channel.socket.nio.SocketSendBufferPool$UnpooledSendBuffer.transferTo(SocketSendBufferPool.java:203)[netty-3.9.4.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.write0(AbstractNioWorker.java:201)[netty-3.9.4.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.writeFromTaskLoop(AbstractNioWorker.java:151)[netty-3.9.4.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioChannel$WriteTask.run(AbstractNioChannel.java:335)[netty-3.9.4.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:372)[netty-3.9.4.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:296)[netty-3.9.4.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)[netty-3.9.4.Final.jar:na] at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)[netty-3.9.4.Final.jar:na] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)[netty-3.9.4.Final.jar:na] at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)[netty-3.9.4.Final.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[na:1.8.0_77] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[na:1.8.0_77] at java.lang.Thread.run(Thread.java:745)[na:1.8.0_77]

    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
    Once, 3 months ago
    Unknown user
    Once, 11 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 4 weeks ago
    Unknown user
    Once, 10 months ago
    423 more bugmates