[JIRA] (JENKINS-16345) CLI does not work through reverse proxy
Lars Klonowski created JENKINS-16345 CLI does not work through reverse proxy Issue Type: Bug Assignee: Unassigned Components: cli Created: 15/Jan/13 12:31 PM Description: 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 log only shows that the timeout has been reached and the connection is therefore closed: (70007)The timeout specified has expired: Error reading chunk Project: Jenkins Priority: Major Reporter: Lars Klonowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16345) CLI does not work through reverse proxy
Lars Klonowski
updated JENKINS-16345
CLI does not work through reverse proxy
Change By:
Lars Klonowski
(15/Jan/13 1:11 PM)
Description:
WhentryingtocontactaJenkins(version1.447.2)behindanApachereverseproxyviaJenkinsCLI,thereisnoresponseuntilreverseproxytimeoutisreachedandthentheconnectiongetsclosed.Debuggingintoit,theCLIhangsonthelinewhereitisreadingtheinputstream.Aftertheconnectionwasclosed,theserversanswerStartingHTTPduplexchannelcanbereadfromthatstream.TheCLIterminateswithanEOFException:{code:none}Exceptioninthreadmainjava.io.EOFException:unexpectedstreamterminationathudson.remoting.Channel.init(Channel.java:408)athudson.remoting.Channel.init(Channel.java:366)athudson.remoting.Channel.init(Channel.java:327)athudson.remoting.Channel.init(Channel.java:323)athudson.remoting.Channel.init(Channel.java:311)athudson.cli.CLI.connectViaHttp(CLI.java:124)athudson.cli.CLI.init(CLI.java:107)athudson.cli.CLI.init(CLI.java:85)athudson.cli.CLI._main(CLI.java:300)athudson.cli.CLI.main(CLI.java:245){code}Theserverdoesnotloganyerrorsandjudgingfromtheinputstreamscontentiswascontactedproperly.Thereverseproxy
error
log
onlyshowsthatthe
whenreaching
timeout
hasbeenreachedandtheconnectionisthereforeclosed
:{
{
code:none}
(70007)Thetimeoutspecifiedhasexpired:Errorreadingchunk
(104)Connectionresetbypeer:Errorreadingchunk(-3)Unknownerror18446744073709551613:proxy:prefetchrequestbodyfailed{code
}
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
