[JIRA] (JENKINS-39289) Better diagnostics on "Backing channel is disconnected"

[k...@kohsuke.org (JIRA)]

Title: Message Title

Kohsuke Kawaguchi created an issue   Jenkins / JENKINS-39289 Better diagnostics on "Backing channel is disconnected" Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: remoting Created: 2016/Oct/27 12:43 AM Priority: Minor Reporter: Kohsuke Kawaguchi 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. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.