hudson.remoting.RequestAbortedException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Slaves disconnecting?
    via by David Kennedy,
  • Problems with memory usage on 1.560
    via by Tobias Hieta,
  • A user of 1.554.2 reported an error apparently similar to JENKINS-10582 causing builds to often fail in cleanup: {code:none} hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:722) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:912) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:608) at ... {code} with a HotSpot crash mentioning JNA: {code:none} EXCEPTION_ACCESS_VIOLATION ... j com.sun.jna.Native.free(J)V+0 j com.sun.jna.Memory.free(J)V+1 j com.sun.jna.Memory.dispose()V+4 j com.sun.jna.Memory.finalize()V+1 v ~StubRoutines::call_stub j java.lang.ref.Finalizer.invokeFinalizeMethod(Ljava/lang/Object;)V+0 J java.lang.ref.Finalizer$FinalizerThread.run()V v ~StubRoutines::call_stub {code} The problem disappeared when passing {{-Dhudson.util.ProcessTree.disable=true}} to Jenkins. However this was just luck: there was no indication from either error message that {{ProcessTree}} was involved, as opposed to some other code running on the slave that happened to use JNA. (file deletion, SVNKit, etc.) To narrow down problems to either JNA or a JRE bug, it would be better to have a single option that stops a given slave (or any slave, or even the master too) from using JNA in any way. Perhaps this could be enforced in the slave class loader by refusing to transfer {{com/sun/jna/\*/\*.\{so,dll,jnalib}}}.
    via by Jesse Glick,
  • I am using the option for creating slaves through command executed on master. This is the error: {code} <===[JENKINS REMOTING CAPACITY]===>Exception in thread "main" java.io.StreamCorruptedException: invalid stream header: 090CACED at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:40) at hudson.remoting.ChannelBuilder.makeTransport(ChannelBuilder.java:259) at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:220) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:149) at hudson.remoting.Launcher.main(Launcher.java:507) at hudson.remoting.Launcher.runWithStdinStdout(Launcher.java:457) at hudson.remoting.Launcher.run(Launcher.java:238) at hudson.remoting.Launcher.main(Launcher.java:192) ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:443) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:339) at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) 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:744) ERROR: Connection terminated java.io.IOException: Unexpected EOF at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:90) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:33) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected EOF at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:90) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:33) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) {code} I have captured (with a `tee` command) this output sent by the slave: {code} <===[JENKINS REMOTING CAPACITY]===>rO0ABXNyABpodWRzb24ucmVtb3RpbmcuQ2FwYWJpbGl0eQAAAAAAAAABAgABSgAEbWFza3hwAAAAAAAAAP4= {code} I have tried slave options like -text and definition of encoding without success. My integration with Jenkins has come to a dead end
    via by Giuseppe Mazzotta,
  • I am using the option for creating slaves through command executed on master. This is the error: {code} <===[JENKINS REMOTING CAPACITY]===>Exception in thread "main" java.io.StreamCorruptedException: invalid stream header: 090CACED at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:40) at hudson.remoting.ChannelBuilder.makeTransport(ChannelBuilder.java:259) at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:220) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:149) at hudson.remoting.Launcher.main(Launcher.java:507) at hudson.remoting.Launcher.runWithStdinStdout(Launcher.java:457) at hudson.remoting.Launcher.run(Launcher.java:238) at hudson.remoting.Launcher.main(Launcher.java:192) ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:443) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:339) at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) 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:744) ERROR: Connection terminated java.io.IOException: Unexpected EOF at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:90) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:33) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected EOF at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:90) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:33) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) {code} I have captured (with a `tee` command) this output sent by the slave: {code} <===[JENKINS REMOTING CAPACITY]===>rO0ABXNyABpodWRzb24ucmVtb3RpbmcuQ2FwYWJpbGl0eQAAAAAAAAABAgABSgAEbWFza3hwAAAAAAAAAP4= {code} I have tried slave options like -text and definition of encoding without success. My integration with Jenkins has come to a dead end
    via by Giuseppe Mazzotta,
  • A user of 1.554.2 reported an error apparently similar to JENKINS-10582 causing builds to often fail in cleanup: {code:none} hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:722) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:912) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:608) at ... {code} with a HotSpot crash mentioning JNA: {code:none} EXCEPTION_ACCESS_VIOLATION ... j com.sun.jna.Native.free(J)V+0 j com.sun.jna.Memory.free(J)V+1 j com.sun.jna.Memory.dispose()V+4 j com.sun.jna.Memory.finalize()V+1 v ~StubRoutines::call_stub j java.lang.ref.Finalizer.invokeFinalizeMethod(Ljava/lang/Object;)V+0 J java.lang.ref.Finalizer$FinalizerThread.run()V v ~StubRoutines::call_stub {code} The problem disappeared when passing {{-Dhudson.util.ProcessTree.disable=true}} to Jenkins. However this was just luck: there was no indication from either error message that {{ProcessTree}} was involved, as opposed to some other code running on the slave that happened to use JNA. (file deletion, SVNKit, etc.) To narrow down problems to either JNA or a JRE bug, it would be better to have a single option that stops a given slave (or any slave, or even the master too) from using JNA in any way. Perhaps this could be enforced in the slave class loader by refusing to transfer {{com/sun/jna/\*/\*.\{so,dll,jnalib}}}.
    via by Jesse Glick,
    • hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:722) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) at com.sun.proxy.$Proxy78.join(Unknown Source)
    No Bugmate found.