Jenkins-CLI does not work with Jenkins behind reverse proxy

92 views
Skip to first unread message

Lars Klonowski

unread,
Jan 3, 2013, 7:26:47 AM1/3/13
to jenkins...@googlegroups.com
When trying to contact a Jenkins (1.447.2) behind a 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 Client 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 log only shows that the timeout has been reached and the connection is therefore closed:
(70007)The timeout specified has expired: Error reading chunk

Is this a known issue and is there any way to establish a connection through a reverse proxy?
Reply all
Reply to author
Forward
0 new messages