Mark Phippard wrote:
> On 6/14/07, Thomas Hallgren <thomas@tada.se> wrote:
>> Mark Phippard wrote:
>> > If you are constructing them yourself, try just making one. That is
>> > the change I am playing with.
>> >
>> > Your best bet would be to write some kind of test code directly
>> > against SVNClient and then ask the Subversion devs.
>> >
>> > Mark
>> >
>> OK, I'm cross-posting this to dev@subversion.tigris.org.
>>
>> I tried using one single instance of the client adapter and it doesn't
>> help. It seems that all methods that I call opens up a socket that then
>> lingers for four minutes. The number of sockets in TIME_WAIT quickly
>> increase to >100.
>>
>> These are the methods that I call during resolution:
>>
>> getList(SVNUrl, SVNRevision, boolean)
>> getContent(SVNUrl, SVNRevision)
>> getDirEntry(SVNUrl, SVNRevision)
>
> svnClientAdapter is a pretty thin wrapper around JavaHL, but it would
> still be useful if you wrote some test code that used only the JavaHL
> classes and created the same problem.
>
I'll try to find some time to do that.
> You are using SVN 1.4.3? What communication protocol to what version
> of the server?
I'm using Subclipse 1.0.5 or 1.2.2. Same problem in both and same
problem with both JavaHL and SVNKit. I have Subversion 1.4.2 installed
on my machine.
>
> Eclipse.org is running svn+ssh, are you also testing this with other
> servers?
>
For these tests I've used svn and not svn+ssh against Eclipse.org. The
person who originally reported the problem was using another server.
- thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Thu Jun 14 19:38:08 2007