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 tigase.org by Unknown author, 1 year ago
via Google Groups by Minho Kang, 1 year ago
via nabble.com by Unknown author, 1 year ago
Connection reset by peer
via hbase-user by 聪聪, 1 year ago
via Stack Overflow by Deepu
, 9 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:379)	at tigase.io.SocketIO.read(SocketIO.java:307)	at tigase.net.IOService.readData(IOService.java:1035)	at tigase.xmpp.XMPPIOService.processSocketData(XMPPIOService.java:650)	at tigase.net.IOService.call(IOService.java:265)	at tigase.net.IOService.call(IOService.java:104)	at java.util.concurrent.FutureTask.run(FutureTask.java:262)	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)	at java.util.concurrent.FutureTask.run(FutureTask.java:262)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)	at java.lang.Thread.run(Thread.java:745)