Details
-
Improvement
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
In order to diagnose a Jenkins master that developed a remoting related problem (such as channel clogging), we want remoting to be able to provide detailed statistics for a channel, and support core plugin to be able to pull this information into a bundle.
Attachments
Issue Links
Activity
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))
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
src/main/java/com/cloudbees/jenkins/support/impl/RemotingDiagnostics.java
http://jenkins-ci.org/commit/support-core-plugin/5f2f23de4e674a6ca22a1a0578b9c0ffa7a58c7a
Log:
Merge pull request #78 from jenkinsci/JENKINS-39150
[FIXED JENKINS-39150] report remoting diagnostics when it's available
Compare: https://github.com/jenkinsci/support-core-plugin/compare/c05e6e1026fa...5f2f23de4e67
Code changed in jenkins
User: Oleg Nenashev
Path:
pom.xml
src/main/java/hudson/remoting/Channel.java
http://jenkins-ci.org/commit/remoting/9dc931703eb89ceb7608b88c0dd04da36f528a3b
Log:
JENKINS-39150- API stabilization && compliance with the compatibility policy (#125)JENKINS-39150- Restrict the newly introduced APIs in stable-2.x branchJENKINS-39150- Fix error processing in the diagnostics dump APIJENKINS-39150- Fix TyposJENKINS-39150- Even more diagnostics according to comments from @stephencJENKINS-39150- Statistic counters are long volatile nowAddresses comments from @oleg-nenashev and @rsandell
JENKINS-39150- Address comment from @oleg-nenashev about conflict with #109JENKINS-39150- Fix another typo