[JIRA] (JENKINS-39289) Better diagnostics on "Backing channel is disconnected"
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Unfortunately I have no capacity to work on Remoting in medium term, so I will unassign it and let others to take it. If somebody is interested to submit a pull request, I will be happy to help to get it reviewed and released. Jenkins / JENKINS-39289 Better diagnostics on "Backing channel is disconnected" Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
[JIRA] (JENKINS-39289) Better diagnostics on "Backing channel is disconnected"
Title: Message Title Oleg Nenashev commented on JENKINS-39289 Re: Better diagnostics on "Backing channel is disconnected" Jan Duris why have you reopened it? Could you please clarify the status? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
[JIRA] (JENKINS-39289) Better diagnostics on "Backing channel is disconnected"
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-39289 Better diagnostics on "Backing channel is disconnected" Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
[JIRA] (JENKINS-39289) Better diagnostics on "Backing channel is disconnected"
Title: Message Title Oleg Nenashev commented on JENKINS-39289 Re: Better diagnostics on "Backing channel is disconnected" The fix has been integrated towards jenkins-2.31 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.
[JIRA] (JENKINS-39289) Better diagnostics on "Backing channel is disconnected"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39289 Re: Better diagnostics on "Backing channel is disconnected" Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/jenkins/7a948d399585d201c4132597aed5723a495acf69 Log: Update remoting to 2.31 in the Jenkins core. (#2628) The change introduces one serious bugfix (JENKINS-39596) and a bunch of various diagnostics improvements. Bugfixes: JENKINS-39596(https://issues.jenkins-ci.org/browse/JENKINS-39596) - Jenkins URL in `hudson.remoting.Engine` was always `null` since `3.0`. It was causing connection failures of Jenkins JNLP agents when using Java Web Start. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) JENKINS-39617(https://issues.jenkins-ci.org/browse/JENKINS-39617) - `hudson.remoting.Engine` was failing to establish connection if one of the URLs parameter in parameters was malformed. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) Improvements: JENKINS-39150(https://issues.jenkins-ci.org/browse/JENKINS-39150) - Add logic for dumping diagnostics across all the channels. (PR #122(https://github.com/jenkinsci/remoting/pull/122), PR #125(https://github.com/jenkinsci/remoting/pull/125)) JENKINS-39543(https://issues.jenkins-ci.org/browse/JENKINS-39543) - Improve the caller/callee correlation diagnostics in thread dumps. (PR #119(https://github.com/jenkinsci/remoting/pull/119)) JENKINS-39290(https://issues.jenkins-ci.org/browse/JENKINS-39290) - Add the `org.jenkinsci.remoting.nio.NioChannelHub.disabled` flag for disabling NIO (mostly for debugging purposes). (PR #123(https://github.com/jenkinsci/remoting/pull/123)) JENKINS-38692(https://issues.jenkins-ci.org/browse/JENKINS-38692) - Add extra logging to help diagnosing `IOHub` Thread spikes. (PR #116(https://github.com/jenkinsci/remoting/pull/116)) JENKINS-39289(https://issues.jenkins-ci.org/browse/JENKINS-39289) - When a proxy fails, report what caused the channel to go down. (PR #128(https://github.com/jenkinsci/remoting/pull/128)) Add Comment
[JIRA] (JENKINS-39289) Better diagnostics on "Backing channel is disconnected"
Title: Message Title Oleg Nenashev resolved as Fixed The fix has been integrated towards remoting-3.1 Jenkins / JENKINS-39289 Better diagnostics on "Backing channel is disconnected" Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-39289) Better diagnostics on "Backing channel is disconnected"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39289 Re: Better diagnostics on "Backing channel is disconnected" Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/Channel.java src/main/java/hudson/remoting/RemoteInvocationHandler.java http://jenkins-ci.org/commit/remoting/0d8a2af7cffa6aa5a6f2675e810b286a984af04e Log: JENKINS-39289 When a proxy fails, report what caused the channel to go down (#128) Today, this requires out of bound knowledge about which connection the proxy was representing, then use other means to figure out why it has failed. This exception chaining shortens that step and makes it easy to find the cause as to why the channel was shut down. 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.
[JIRA] (JENKINS-39289) Better diagnostics on "Backing channel is disconnected"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39289 Re: Better diagnostics on "Backing channel is disconnected" Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/Channel.java src/main/java/hudson/remoting/RemoteInvocationHandler.java http://jenkins-ci.org/commit/remoting/89a1774918d1e2adba41ae7ae4ba34f095dc2676 Log: JENKINS-39289 When a proxy fails, report what caused the channel to go down Today, this requires out of bound knowledge about which connection the proxy was representing, then use other means to figure out why it has failed. This exception chaining shortens that step and makes it easy to find the cause as to why the channel was shut down. 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.
[JIRA] (JENKINS-39289) Better diagnostics on "Backing channel is disconnected"
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:26at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:184) 15:44:26at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249) 15:44:26at com.sun.proxy.$Proxy104.isAlive(Unknown Source) 15:44:26at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:996) 15:44:26at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:166) 15:44:26at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:853) 15:44:26at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) 15:44:26at hudson.model.Run.execute(Run.java:1738) 15:44:26at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) 15:44:26at hudson.model.ResourceController.execute(ResourceController.java:98) 15:44:26at hudson.model.Executor.run(Executor.java:410) The error diagnostics is easier if the cause of the channel loss is linked to this exception.
