|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
@Jesse: we discovered this was being caused when we accessed our Jenkins instance through a proxy. After some digging we stumbled across https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache which mentions setting the proxy-nokeepalive value in our apache config. After setting that value, all our issues went away. The 404's and stack trace in the jenkins log were related, albeit loosely. When the proxied connection broke down, apache would return a 404, and Jenkins would spit out the ClientSocketException.
We discovered this when one of our developers mentioned he always accessed Jenkins directly rather than through our proxy and he had never had issues. With a little wget magic we saw he was absolutely right, which set us on the right path.
Here's hoping this helps everyone else out...