-
Improvement
-
Resolution: Fixed
-
Minor
-
None
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
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