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. ,
    via GitHub by ritchieGitHub

    Set larger socket timeout (or 0 to set no timeout).

  2. ,
    via github.com by Unknown author

    Upgrade your nanohttpd

Solutions on the web

via Jenkins JIRA by Nick Sieger, 1 year ago
via Jenkins JIRA by Nick Sieger, 1 year ago
via Jenkins JIRA by Jes Struck, 1 year ago
via Jenkins JIRA by Jes Struck, 1 year ago
via Stack Overflow by OrwellHindenberg
, 2 years ago
via Jenkins JIRA by Donal McNamee, 1 year ago
java.net.SocketException: Connection reset	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96)	at java.net.SocketOutputStream.write(SocketOutputStream.java:136)	at winstone.ClientOutputStream.write(ClientOutputStream.java:39)	at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:181)	at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:119)	at winstone.WinstoneOutputStream.write(WinstoneOutputStream.java:112)	at java.io.OutputStream.write(OutputStream.java:58)	at hudson.remoting.ProxyOutputStream$Chunk$1.run(ProxyOutputStream.java:185)	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)	at java.util.concurrent.FutureTask.run(FutureTask.java:138)	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)	at java.lang.Thread.run(Thread.java:619)