|
||||||||
|
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.
Just to close the loop, what I have found is that this issue is related to garbage collection in the underlying JVM. I installed the monitoring plugin that uses JavaMelody (see https://wiki.jenkins-ci.org/display/JENKINS/Monitoring), and if I trigger two successive garbage collections before the bulk of the builds run, then I don't get this error any more. (The clue came from this post: http://jenkins-ci.361315.n4.nabble.com/Hudson-garbage-collection-on-schedule-td3050696.html). From looking at the graphs generated by the plugin, what seems to happen is that if there is too much VM available, then the amount of time that garbage collection takes when it finally is triggered exceeds the amount of time required to maintain the connection to SVN. I have not characterized the times involved, just noted empirically that starting my daily builds runs with the smallest amount of VM possible seems to help a lot.
Maybe there's such a thing as having too much VM?
Perhaps mention of this could be made in the "setting up Jenkins" articles?