Checkouts of some SVN repositories dying using TortoiseSVN 1.8.x

I’ve come across a problem that’s reproducible with at least two people here, possibly more. I checked all of your online resources and could find nothing pertaining to this problem. I also spent a couple of hours on the web searching for anyone who had seen this problem before, without success.

We’re trying to perform a check out of a 65MB Subversion repository. In all cases, SVN Checkout is used. The URL of the Subversion repository is confirmed each time, as is the destination on the Windows disk.

• Using version 1.7.13.24257, there were no problems

• I upgraded to 1.8.0.24401, removed the repository I had just checked out from the Windows disk, and repeated the checkout operation. It failed. After a reboot and another try, it failed again.

• I upgraded to 1.8.1.24570, removed the directories I had just tried to load the repository into, and tried to do another checkout. It also failed. A reboot and another try yielded the same result.

• I uninstalled 1.8.1, rebooted, and installed 1.7.13 again. The checkout worked fine when I went back.

The error message on the client side with the 1.8.x TortoiseSVN clients was:
An existing connection was forcibly closed by the remote host

I also checked the httpd error_log on the SVN server. There were two errors reported:
[Wed Aug 07 11:37:14 2013] [error] [client 10.224.235.94] Provider encountered an error while streaming a REPORT response. [500, #0]
[Wed Aug 07 11:37:14 2013] [error] [client 10.224.235.94] A failure occurred while driving the update report editor [500, #103]

So the problem is only occurring with the 1.8.x versions. The Subversion server is running version 1.8.1

Thanks in advance,
Keith

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3062214

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-07 19:49:05 CEST