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. ,

    Normally, the connection to an HTTP server is closed after each response. Change the network connection and make sure the network is stable when making the request. When the server closes such a connection the client usually reopens it again.

Solutions on the web

via Google Groups by Shobitha S, 1 year ago
via Stack Overflow by Daniel Li
, 11 months ago
via GitHub by honyee
, 1 year ago
via Stack Overflow by kason
, 1 month ago
via GitHub by lijunyong
, 10 months ago
java.io.IOException: Connection reset by peer	at sun.nio.ch.FileDispatcherImpl.read0(Native Method)	at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)	at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)	at sun.nio.ch.IOUtil.read(IOUtil.java:192)	at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)	at io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(PooledUnsafeDirectByteBuf.java:221)	at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:898)	at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:242)	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119)	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:528)	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:485)	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:399)	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:371)	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)	at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)	at java.lang.Thread.run(Thread.java:745)