On Tue, Mar 9, 2010 at 2:37 PM, Steffen Sledz <sledz_at_dresearch.de> wrote:
> Johan Corveleyn wrote:
>> You could be experiencing a client-side timeout. Svn with neon (which
>> is the default client-side http access library) has a default timeout
>> of 30 seconds. If the client doesn't get something within those 30
>> seconds, it terminates the connection.
>> You can specify a higher timeout value in the "runtime configuration
>> area" on the client, in the servers file. E.g. put a line
>> "http-timeout = 60" in the global section, or in the group that
>> matches with your server.
>>  http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html
>>  http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html#svn.advanced.confarea.opts.servers
> I tried this without success.
> But i did not expect success here, because the error occurred after
> about 15 minutes what is much longer than the http-timeout.
[ Remember to put the list in cc as well, so the reply goes not only to me ]
It could be a timeout on the server as well. Look into the SVN
server's Apache config for a TimeOut directive ...
That the total operation took more than 15 minutes doesn't mean
anything for this kind of timeout, because during the entire operation
a lot of different http requests/responses are exchanged (you can see
which if you analyze your Apache's access logs). The entire sequence
of requests/responses can take hours. As long as no single request has
to wait more than 30 seconds for its response you'll be fine. If a
single http request doesn't get a response in 30 seconds (or whatever
custom value you've configured) you'll get a timeout ...
Alternatively, in your setup (with squid proxy and firewalls etc in
between), it could also be one of those components in the middle that
decides to terminate the connection.
Received on 2010-03-09 15:07:11 CET