Hello Jeff, The files must be locked from a previous SVN update. I would recommend that you add the cleanCopy tag to your sourcecontrol block for each project.
<sourcecontrol type="svn"> <cleanCopy>True</cleanCopy> </sourcecontrol> Thank you Thon Becker ----- Original Message ---- From: Jeff <[email protected]> To: ccnet-user <[email protected]> Sent: Wed, June 16, 2010 7:44:41 AM Subject: [ccnet-user] Connectivity issues - "existing connection was forcibly closed by the remote host" I am having trouble diagnosing this error message. I'm not sure if it is a problem with SVN, CCNET, the network, or the SVN machine. ***** ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation failed: svn: Can't read from connection: An existing connection was forcibly closed by the remote host. Process command: svn log svn://<my repo address> -r "{2010-06-16T04:55:17Z}:{2010-06-16T06:28:26Z}" --verbose --xml -- username <my username> --password ******** --no-auth-cache --non- interactive <remainder of stack trace omitted> ***** I have a few dozen builds set up on ccnet. ccnet pulls the source from svn. A few times an hour, I get the above error message on my interval triggered builds. A few times an hour means that most of the time, the interval is working and getting a response. Indeed, I often see builds starting and completing while watching the dashboard. But for some reason, all repos seem to error out every hour or so. Has anyone else run into this? Any idea what could be causing it? Our network guy say the traffic looks fine and there isnt a problem with the network dropping out. I see nothing in the server logs of either the svn server or the ccnet server. Next, I am going to try upgrading to the lastest version of SVN and testing a repo on https:// instead of svn://
