Provide escape hatch for a possible NIO remoting bug

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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

            Assignee:
            Kohsuke Kawaguchi
            Reporter:
            Kohsuke Kawaguchi
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: