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

Re: Timeout

From: Ben Johnson <ben_at_indietorrent.org>
Date: Tue, 18 Dec 2012 10:10:50 -0500

On 12/18/2012 8:55 AM, David Earl wrote:
> Since moving a repository to a server outside my control, I get a timeout when accessing the repository for the first time each day:
> ------
> Update <path> Unable to connect to a repository at URL
> 'https://...' OPTIONS of
> 'https://...': Could not
> read status line: connection was closed by server
> (https://..)
> ------
> The repository authentication is via Kerberos, and I am told that Kerberos keeps a user ticket (like a session) for 8 hours after which inactivity it acquires a new one. This seems to take a lot longer than when the session is already active.
> So when I do an update, for example, at the start of a day, I get the error message. But it seems the login has cached its session, because I then repeat the update and it works.
> It looks like the timeout is not long enough. I can't see anything in the Settings that would allow me to increase the timeout.
> Is my theory likely? If not what could be causing it? And how can the timeout be increased?

I asked a very similar question a few weeks ago:

I still don't know what causes this, unfortunately. I suspect that the
problem results from multiple factors -- namely, some element of the
Apache configuration coupled with some element of TSVN.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-12-18 16:11:12 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.