|
||||||||
|
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.
I'm grasping at anything that might alleviate the situation. Configuring httpd to maintain an established connection for a while to see if there was any more activity that could be sent across it before dismantling sounded like a reasonable thing to try.
From the experiment where I ran the same check-outs against both a revision 1.6 repo and a newly-installed 1.8 repo (Dell R620, two six-core processors, 32 GB RAM, 10K RPM SAS drives, CentOS 6.3), the fact that the problem occurs on both repos suggests that the problem is not on the Subversion side – it's on the Jenkins server side. Anyone with suggestions about Jenkins or CentOS configuration that might help this, please speak up! It's killing one or two out of 23 builds every day.