Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16345

CLI does not work through reverse proxy

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • cli
    • None

      When trying to contact a Jenkins (version 1.447.2) behind an Apache reverse proxy via Jenkins CLI, there is no response until reverse proxy timeout is reached and then the connection gets closed.

      Debugging into it, the CLI hangs on the line where it is reading the input stream. After the connection was closed, the server's answer "Starting HTTP duplex channel" can be read from that stream.

      The CLI terminates with an EOFException:

      Exception in thread "main" java.io.EOFException: unexpected stream termination
        at hudson.remoting.Channel.<init>(Channel.java:408)
        at hudson.remoting.Channel.<init>(Channel.java:366)
        at hudson.remoting.Channel.<init>(Channel.java:327)
        at hudson.remoting.Channel.<init>(Channel.java:323)
        at hudson.remoting.Channel.<init>(Channel.java:311)
        at hudson.cli.CLI.connectViaHttp(CLI.java:124)
        at hudson.cli.CLI.<init>(CLI.java:107)
        at hudson.cli.CLI.<init>(CLI.java:85)
        at hudson.cli.CLI._main(CLI.java:300)
        at hudson.cli.CLI.main(CLI.java:245)

      The server does not log any errors and judging from the input stream's content is was contacted properly.

      The reverse proxy error log when reaching timeout:

      (70007)The timeout specified has expired: Error reading chunk
(104)Connection reset by peer: Error reading chunk
(-3)Unknown error 18446744073709551613: proxy: prefetch request body failed

        1. 16345-threadDump-client.txt
          4 kB
        2. 16345-threadDump-Master.txt
          31 kB

            Unassigned Unassigned
            laccu Lars Klonowski
            Votes:
            10 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: