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 JBoss Issue Tracker by Timothy Heider, 1 year ago
Connection reset by peer
via nabble.com by Unknown author, 1 year ago
Connection reset by peer
via hbase-user by 聪聪, 2 years ago
via Stack Overflow by Deepu
, 1 year ago
java.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method)[rt.jar:1.7.0_21] at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)[rt.jar:1.7.0_21] at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:225)[rt.jar:1.7.0_21] at sun.nio.ch.IOUtil.read(IOUtil.java:193)[rt.jar:1.7.0_21] at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:359)[rt.jar:1.7.0_21] at org.xnio.nio.NioSocketConduit.read(NioSocketConduit.java:262)[xnio-nio-3.1.0.CR3.jar:3.1.0.CR3] at org.xnio.conduits.ConduitStreamSourceChannel.read(ConduitStreamSourceChannel.java:127)[xnio-api-3.1.0.CR3.jar:3.1.0.CR3] at io.undertow.server.HttpReadListener.handleEvent(HttpReadListener.java:83) at io.undertow.server.HttpReadListener.handleEvent(HttpReadListener.java:43) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91)[xnio-api-3.1.0.CR3.jar:3.1.0.CR3] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:61)[xnio-api-3.1.0.CR3.jar:3.1.0.CR3] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:85)[xnio-nio-3.1.0.CR3.jar:3.1.0.CR3] at org.xnio.nio.WorkerThread.run(WorkerThread.java:528)[xnio-nio-3.1.0.CR3.jar:3.1.0.CR3]