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

TSVN connection to repository times-out after server is idle for some period of time (408 errors in Apache logs)

From: Ben Johnson <ben_at_indietorrent.org>
Date: Mon, 19 Nov 2012 11:33:17 -0500

Hi, everyone,

This may be more of an Apache question than a TortoiseSVN question, so
please let me know if this has nothing to do with TSVN.

If I haven't connected to an SVN repository on the server in question
for some period of time (e.g., overnight), Apache logs a 408 error the
first time I try to connect (regardless of whether I'm updating,
committing, etc.):

XXX.XXX.XXX.XXX - - [05/Nov/2012:06:44:05 -0800] "-" 408 0 "-" "-"

The TSVN error dialog says:

Command Commit
Error Commit failed (details follow):
Error Unable to connect to repository at URL
Error 'https://example.com/svn/project/trunk'
Error OPTIONS of 'https://example.com/svn/project/trunk': Could not read
Error status line: connection was closed by server (https://example.com)

If I simply re-try the action, everything works as expected for the
remainder of the day (presumably because someone is hitting the server
often enough to prevent the timeout issue from occurring).

Is this issue due to anything that TSVN is doing? Or is this related to
Apache's mod_reqtimeout module (or similar)?

On the server in question, SVN requests are handled via Apache's
mod_dav_svn and mod_authz_svn modules.

Thanks for any guidance in this regard,



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-11-19 17:33:34 CET

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

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