Glad to hear it. We had similar problems using svnsync when performing the initial sync. We had a couple of historic commits of a lot of third-party libraries that were very large. We had to bump the timeout up to 600 sec. to get svnsync to complete the sync. Now that we are syncing happily along, we will probably turn it back down to 300.
Regards, Tom From: Wadhavankar, Hemant [mailto:hemant.wadhavan...@lsi.com] Sent: Thursday, May 20, 2010 3:17 AM To: Thomas Loy; users@subversion.apache.org Subject: RE: SVN Error Hey - setting Timeout as 300 resolved the problem. Best, Hemant Unstoppable...... From: Wadhavankar, Hemant Sent: Thursday, May 20, 2010 10:27 AM To: 'Thomas Loy'; users@subversion.apache.org Subject: RE: SVN Error Thanks Tom. I am using http and not https. I noticed "Timeout 300" in conf/extra/httpd-default.conf - but it is not getting called (include) in httpd.conf. So I will play around with it. Best, Hemant Unstoppable...... From: Thomas Loy [mailto:thomas....@cbeyond.net] Sent: Wednesday, May 19, 2010 8:50 PM To: Wadhavankar, Hemant; users@subversion.apache.org Subject: RE: SVN Error That would be the first thing I would do. What is the current timeout? Are you trying to use http or https? Regards, Tom From: Wadhavankar, Hemant [mailto:hemant.wadhavan...@lsi.com] Sent: Wednesday, May 19, 2010 10:58 AM To: users@subversion.apache.org Subject: SVN Error Hello, I am getting an error like this. I am using SVN 1.6.11 and Apache 2.2.14 svn: REPORT of '/!svn/vcc/default': Could not read response body: connection was closed by server I tried SVN checkout using file:///<file:///\\> method and it did not have any issues. Will changing "Timeout" in Apache configuration will help here? Best, Hemant Unstoppable......
