Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39289

Better diagnostics on "Backing channel is disconnected"

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • remoting
    • None

      Often, the code that handles lost connection and report that problem is different from code that uses proxies that go over this channel. Example stack trace:

      15:44:26 java.io.IOException: Backing channel is disconnected.
15:44:26        at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:184)
15:44:26        at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249)
15:44:26        at com.sun.proxy.$Proxy104.isAlive(Unknown Source)
15:44:26        at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:996)
15:44:26        at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:166)
15:44:26        at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:853)
15:44:26        at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
15:44:26        at hudson.model.Run.execute(Run.java:1738)
15:44:26        at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
15:44:26        at hudson.model.ResourceController.execute(ResourceController.java:98)
15:44:26        at hudson.model.Executor.run(Executor.java:410)

      The error diagnostics is easier if the cause of the channel loss is linked to this exception.

            Unassigned Unassigned
            kohsuke Kohsuke Kawaguchi
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: