[JIRA] (JENKINS-39543) Improve the caller/callee correlation diagnostics
Title: Message Title Oleg Nenashev edited a comment on JENKINS-39543 Re: Improve the caller/callee correlation diagnostics 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-39543) Improve the caller/callee correlation diagnostics
Title: Message Title Oleg Nenashev commented on JENKINS-39543 Re: Improve the caller/callee correlation diagnostics The fix has been integrated towards 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-39543) Improve the caller/callee correlation diagnostics
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39543 Re: Improve the caller/callee correlation diagnostics 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-39543) Improve the caller/callee correlation diagnostics
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39543 Re: Improve the caller/callee correlation diagnostics Code changed in jenkins User: Oleg Nenashev Path: CHANGELOG.md http://jenkins-ci.org/commit/remoting/fa398e1aa531dd4cb84d01d37a683f47721f9816 Log: Changelog: Amend JENKINS-39543 integration in #119 towards 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-39543) Improve the caller/callee correlation diagnostics
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39543 Re: Improve the caller/callee correlation diagnostics Code changed in jenkins User: Oleg Nenashev Path: CHANGELOG-2.x.md http://jenkins-ci.org/commit/remoting/8b74568e7ae7db2e155f3d4695024002f21feb71 Log: Changelog: Amend JENKINS-39543 integration in #119 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-39543) Improve the caller/callee correlation diagnostics
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-39543 Improve the caller/callee correlation diagnostics Issue Type: Improvement Assignee: Unassigned Components: remoting Created: 2016/Nov/06 10:33 PM Priority: Minor Reporter: Oleg Nenashev Follow-up to https://github.com/jenkinsci/remoting/pull/119 > was trying to diagnose a remoting call that bridges two VMs that is hanging. This can be made easier if thread dump allows us to correlate the caller/callee. This change adds the request ID to thread name so that thread dump will show this clearly Also fixes one incorrect use of toString() in diagnosis, which should be getName() — see all the other uses of thread names. Add Comment
[JIRA] (JENKINS-39543) Improve the caller/callee correlation diagnostics
Title: Message Title Oleg Nenashev resolved as Fixed The fix has been integrated towards 2.62.3 and 3.1 Jenkins / JENKINS-39543 Improve the caller/callee correlation diagnostics 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
