[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Errors while checking out large directory

From: Mark Phippard <markphip_at_gmail.com>
Date: Fri, 15 Jan 2010 15:16:52 -0500

On Fri, Jan 15, 2010 at 3:08 PM, Andy Levy <andy.levy_at_gmail.com> wrote:
> I've found several references to this problem via Google & the list
> archives, but never any answers.
> When checking out from *some* clients (one in particular), I get the
> following errors in my Apache error log on a regular basis:
> [Fri Jan 15 12:33:57 2010] [error] [client IP] Provider encountered an
> error while streaming a REPORT response.  [500, #0]
> [Fri Jan 15 12:33:57 2010] [error] [client IP] A failure occurred
> while driving the update report editor  [500, #190004]
> My SVN server is CollabNet's distribution of 1.5.2 running on Windows
> 2003 with the default configuration of Apache that's included.

This is usually an issue with the client where it is not responding
fast enough and the server thinks the connection has been dropped.
For example, the client can spend so long writing the working copy
that the server thinks it dropped.


There is a timeout in the httpd.conf you can set to make the server
wait longer. I do not recall what it is off the top of my head.

I think if you changed the client to use Serf instead of Neon you
would also avoid this problem. Neon does this all as one giant HTTP
request, where as Serf breaks it up into lots of smaller GET requests.
 So I do not think Serf would likely timeout.

You should be able to just edit the %AppData%\Subversion\servers file
on the client to tell it to use Serf over Neon (assuming your binaries
support it).

http-library = serf

If Anthill uses SVNKit then I am not sure what you can do other than
increase the timeout on the server.

Mark Phippard
Received on 2010-01-15 21:17:30 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.