[JIRA] (JENKINS-39290) Provide escape hatch for a possible NIO remoting bug
Title: Message Title Oleg Nenashev commented on JENKINS-39290 Re: Provide escape hatch for a possible NIO remoting bug 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-39290) Provide escape hatch for a possible NIO remoting bug
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39290 Re: Provide escape hatch for a possible NIO remoting bug 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-39290) Provide escape hatch for a possible NIO remoting bug
Title: Message Title Oleg Nenashev commented on JENKINS-39290 Re: Provide escape hatch for a possible NIO remoting bug The fix has been integrated towards 2.62.3 and 3.1 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-39290) Provide escape hatch for a possible NIO remoting bug
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-39290 Provide escape hatch for a possible NIO remoting bug Change By: SCM/JIRA link daemon 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-39290) Provide escape hatch for a possible NIO remoting bug
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39290 Re: Provide escape hatch for a possible NIO remoting bug Code changed in jenkins User: Kohsuke Kawaguchi Path: docs/configuration.md pom.xml src/main/java/org/jenkinsci/remoting/nio/NioChannelHub.java http://jenkins-ci.org/commit/remoting/6575e82951b7f7c991db49e74261c52e40d1771b Log: Merge pull request #123 from jenkinsci/disable-nio [FIXED JENKINS-39290] A debug flag to disable NIO Compare: https://github.com/jenkinsci/remoting/compare/9dc931703eb8...6575e82951b7 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-39290) Provide escape hatch for a possible NIO remoting bug
Title: Message Title Kohsuke Kawaguchi created an issue Jenkins / JENKINS-39290 Provide escape hatch for a possible NIO remoting bug Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: remoting Created: 2016/Oct/27 12:59 AM Priority: Minor Reporter: Kohsuke Kawaguchi Some of the observed failure modes of remoting (connection is lost and both sides are seemingly not doing anything) makes me suspicious of a possible bug in NIO. In a situation like that, to further isolate problems and to work around the problem, is it convenient to be able to have a switch to bypass NIO and switch back to classic IO. This should be a switch that one can activate without restarting Jenkins Add Comment
