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

Re: Updates and Checouts Failing...

From: Martin Floeer <martin.floeer_at_gmx.de>
Date: Mon, 15 Jun 2009 03:32:31 -0700 (PDT)

kmradke-2 wrote:
> David Weintraub <qazwart_at_gmail.com> wrote on 03/27/2009 09:12:57 AM:
>> I've recently been getting reports about Subversion commands failing.
>> This happens in Eclipse, Tortoise, and the command line. Everyone
>> whose reported on these problems have been on Windows systems. There
>> is no error in the Apache log, they simply get "Server Reset
>> Connection" errors.
>> Here's the latest one that happened while doing an update in Tortoise::
>> (Window Title: C:\eclipse_workspace\neo_ibfiltering - Update -
>> TortoiseSVN Failed!)
>> [...]
>> Added: C:\eclipse_workspace\neo_ibfiltering\adsales\web\dojo-
>> src\dojox\dtl\demos\json\fruit.json
>> Added: C:\eclipse_workspace\neo_ibfiltering\adsales\web\dojo-
>> src\dojox\dtl\demos\json\blog
>> Error Report of '/dev/!svn/vcc/default': Could not read response
>> body: connection was
>> Error closed by server (http://subversion.solbright.com)
>> Finished!
>> This user also reported that they got an "RA layer request failed"
>> while trying to do this via Eclipse.
>> I suspect that there may be an issue with our network or our Apache
>> setup. These are extremely long operations. I wonder if the Apache
>> server is timing out. And, if it is, how can I prevent that from
>> happening.
> Yes, I believe you are running into a network timeout. Subversion
> does a fair amount of disk i/o between network operations to maintain
> the working copy dirs and large files or a slow disk can cause
> the connection to be dropped before the whole transaction is complete.
> (For example, duplicating a 2G file from the .svn folder to the
> working copy folder during the update may take longer than the
> default network timeout)
> In your apache config, I think you want to adjust the Timeout value:
> #
> # Timeout: The number of seconds before receives and sends time out.
> #
> #####Timeout 300
> Timeout 1200
> Beware of setting this too high, since you can easily make
> it much easier for someone to perform a denial of service
> attack against your apache server...
> Kevin R.
> I have the same problem regardless of the Client windows Operating System
> Environment:
> Apache 2.2.8
> Subversion 1.5.6
> Server OS Windows Server 2003 SP
> Nothing odd in the apache error log with log level debug
> Increasing the Apache Timeout does not make any differences.
> Martin F.
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1445358
> To unsubscribe from this discussion, e-mail:
> [users-unsubscribe_at_subversion.tigris.org].

View this message in context: http://www.nabble.com/Updates-and-Checouts-Failing...-tp22742520p24032209.html
Sent from the Subversion Users mailing list archive at Nabble.com.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-15 12:35:56 CEST

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