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

Re: SVN 1.8 timeout fix

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Tue, 14 Oct 2014 18:13:28 +0100

<Paul.Gillis_at_L-3Com.com> writes:

> We just upgraded from Subversion 1.7 to 1.8 and almost immediately
> began getting timeouts checking out larger repositories. The Tortoise
> file transfer rate would quickly diminish to 0 and eventually return
> an error. The subversion command client would terminate with "svn
> E175012 Connection timed out." I found several reports from other who
> encountered the same thing, but there were no solutions offered. Some
> people said they simply reverted back to 1.7.

I assume you are referring to an upgrade of the client from 1.7 to 1.8.
Did you also upgrade the server? Which version is running on the

One change in 1.8 is that serf is used to handle HTTP on the client-side
rather than neon. The default client-side HTTP timeout when using neon
is 60 minutes but when using serf it is 10 minutes. A client can change
its default timeout by setting servers:global:http-timeout.

If you upgraded the server to 1.8 then update/checkout will have
switched to skelta-mode by default and I suppose configuring the client
or server to use bulk-mode might solve the problem:


Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Received on 2014-10-14 19:14:01 CEST

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.