hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset

Jenkins JIRA | Jesse Glick | 2 years ago
  1. 0

    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}}}.

    Jenkins JIRA | 2 years ago | Jesse Glick
    hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
  2. 0

    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}}}.

    Jenkins JIRA | 2 years ago | Jesse Glick
    hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
  3. 0

    ERROR: Processing failed due to a bug in the code - Ryan Knight - net.java.dev.hudson.users - MarkMail

    markmail.org | 2 years ago
    hudson.remoting.RequestAbortedException: java.io.EOFException
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. hudson.remoting.RequestAbortedException

      hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset

      at hudson.remoting.RequestAbortedException.wrapForRethrow()
    2. Hudson :: Remoting Layer
      Channel.call
      1. hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41)
      2. hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34)
      3. hudson.remoting.Request.call(Request.java:174)
      4. hudson.remoting.Channel.call(Channel.java:722)
      4 frames
    3. Hudson
      AbstractBuild$AbstractBuildExecution.run
      1. hudson.Launcher$RemoteLauncher.kill(Launcher.java:912)
      2. hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:608)
      2 frames