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 Jenkins JIRA by Akshay Kumar Sureshchand, 1 year ago
Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@6d4eb0e7[name=BGC-BE-TTACC47]
via Jenkins JIRA by Kamil Bednarczyk, 1 year ago
Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@41241c12[name=Windows2008R2_64bit]
via Stack Overflow by Justin Dunlap
, 1 year ago
Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@1e5cf2e[name=BuildTestSlave]
via by Unknown author, 1 year ago
Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@240c0b4e[name=ST_windows_slave]
via Google Groups by (JIRA), 1 year ago
Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@5a6e25a4[name=Eudekarftps7.8]
via Google Groups by (JIRA), 1 year ago
Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@18bfcae9[name=Arnold] Connection timed out	at Method)	at	at	at	at	at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(	at org.jenkinsci.remoting.nio.FifoBuffer.receive(	at	at jenkins.util.ContextResettingExecutorService$	at java.util.concurrent.Executors$	at	at java.util.concurrent.ThreadPoolExecutor.runWorker(	at java.util.concurrent.ThreadPoolExecutor$	at