From 09c0d9b658374203f5b6ce75926241bc19511c92 Mon Sep 17 00:00:00 2001 From: Oleg Nenashev Date: Sun, 5 Feb 2017 16:34:07 +0100 Subject: [PATCH 1/4] [JENKINS-41730] - Add option to ignore the X-Jenkins-Agent-Protocols header + improve diagnostics - [x] Add the `org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.ignoreJenkinsAgentProtocolsHeader` property, which disables the cache - [x] Print warning in the case if the list of supported protocols is empty - [x] Add documentation --- docs/configuration.md | 12 +++++++-- .../engine/JnlpAgentEndpointResolver.java | 27 ++++++++++++++++++- 2 files changed, 36 insertions(+), 3 deletions(-) diff --git a/docs/configuration.md b/docs/configuration.md index 55b7a2bf2..d7c5a50dd 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -99,10 +99,18 @@ These properties require independent configuration on both sides of the channel. org.jenkinsci.remoting.nio.NioChannelHub.disabled false 2.62.3 - ? + TODO JENKINS-39290 Boolean flag to disable NIO-based socket connection handling, and switch back to classic IO. Used to isolate the problem. - - + + + org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.ignoreJenkinsAgentProtocolsHeader + false + TODO + TODO + JENKINS-41730 + If enabled, the remoting client will ignore the list of supported protocols returned by the server. Then it will try to connect by iterating through available protocols till it finds the server accepts connection. +