[JIRA] [core] (JENKINS-10524) winstone.ClientSocketException: Failed to write to client

Wed, 12 Jun 2013 08:51:46 -0700

 
hardwickj edited a comment on Bug JENKINS-10524

If it were a matter of too many _javascript_ files being loaded than a lot more users would be having this problem.

If you guys are running Jenkins behind an apache proxy, try just hitting jenkins directly for a day and see what your results are. This might require typing a longer URL and appending :8080 at the end, but definitely worth it for debugging reasons.

All our problems went away once we figured out our apache proxying issue. We initially discovered the discrepancy by running the following curl command against jenkins, first through the apache proxy, and second against jenkins directly:

Unable to find source-code formatter for language: bash. Available languages are: _javascript_, sql, xhtml, actionscript, none, html, xml, java
#!/bin/bash

for i in {1..100}
do
  # via proxy
  wget --quiet --spider http://build/api/json?pretty=true
  if [ $? -ne 0 ]; then
    echo "wget failed via proxy"
  fi
done

for i in {1..100}
do
  # bypassing the proxy
  wget --quiet --spider http://jenkins:8080/api/json?pretty=true
  if [ $? -ne 0 ]; then
    echo "wget failed directly"
  fi
done

If you run that and you only see "wget failed via proxy" but nothing directly, then it's your proxy configuration.

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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to