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

RE: [TSVN] TortoiseSVN is not closing server connections in a timely manner

From: Garrick Olson <Garrick.Olson_at_Aceva.com>
Date: 2004-12-03 02:08:45 CET

>> >Are you sure that those connections really are open?
>> Yes. Both the client process and server process show the connection
>> "ESTABLISHED". When the log dialog is closed, I see the connections
>> the server transition to "CLOSE_WAIT" before they disappear.
>In that case, I suggest you report this to the subversion mailing
>list. TSVN doesn't differ between protocolls - that's completely up to
>the Subversion library. So they must do something different when using
>the svn:// protocoll (not closing the connections).

These symptoms do not seem (to me) to be consistent with a server

Why does the client believe the connection is "ESTABLISHED"? If it was
cleaning up properly, and the server was not, I would expect to see the
server confused, but not the client.

At the point I close the log dialog on the client, why does the server
then close the connection? If the client had already done everything in
its power to clean up, what happens at this point that causes the server
to suddenly close the connections?

I did a bit more testing, and found that if I adjust the
"KeepAliveTimeout" in httpd.conf, I can reproduce the problem using the
http protocol.

I think the problem is with the client, and Apache just masks the
symptom because by default it kills off idle connections fairly quickly.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Dec 3 02:09:21 2004

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

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