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

Connections get not closed

From: Joern Mueller <j.mueller_at_fishlabs.net>
Date: Fri, 15 Jun 2012 16:08:58 +0200

Hello all,

 

I'm using the svn 1.7.5 SDK on Win32 with VS2005. (Hope this is the right list, but I thought I'm rather using the SDK than developing on it.) For some reason every call fetching data from the server opens up it's own socket connection but doesn't close it when data retrieval is finished. I tried this with for the functions svn_client_status4(), svn_client_update4() and svn_client_checkout3(), but I guess the problem is not specific to one or some functions. When examining the sockets in TCPView they are generally listed as 'established', some however even pop out of their host process and live on in the system process (PID:0) as 'waiting' for some time. When closing down the application the remaining connections also go the latter way. In this behaviour resutls in hundreds of open connections (e.g. when checking the status of all files of a project) which is more than our server can handle.

Please give me any advice if there is a possiblity to close svn connections by function call or by limiting the life span of connections when they are established. Of course I also will appreciate all other hints and ideas.

 

Kind regards and Thanks in advance

Jörn Müller
Received on 2012-06-15 16:12:28 CEST

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

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