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

Re: Re: Re: Re: TortoiseSVN "Get lock" of multiple files fails via Java-SSL-tunnel since v1.9.0 (bug?)

From: Ivan Zhakov <ivan_at_visualsvn.com>
Date: Mon, 9 May 2016 16:11:48 +0300

On 9 May 2016 at 15:33, David Hinken <d.hinken_at_isfh.de> wrote:
>> On 9 May 2016 at 15:03, David Hinken <d dot hinken at isfh dot de> wrote:
>> >> > Ivan suggested to use the svn command-line tool. I just tried it using a batch file
>> >> > and passed all 1000 text files to 'svn lock a b c ...'. It works fine without any trouble!
>> >> > It seems to work file-by-file and thus takes is slower is quite slow but work without problem.
>> >> It's really strange, because TortoiseSVN uses the same API in the same
>> >> way as Subversion command line client.
>> >>
>> >> What svn.exe version you're testing? You may use 'svn.exe --version'
>> >> command to find Subversion command line client version.
>> >

>> >> I'm not familiar with Java-Tunnel. Could you please share URL you're
>> >> using to checkout Subversion working copy.
>> >
>> > The URL is
>> > https://localhost:35741/svn/Test
>> >
>> > and redirects via the Java-Tunnel (running in Firefox) to the SVN server.
>> >
>> Now it's more clear: Java-Tunnel acts as a proxy and forwards all
>> requests to SVN Server. The most likely problem that Java-Tunnel
>> doesn't implement HTTP pipelining [1] properly. HTTP pipelining is a
>> technique in which multiple HTTP requests are sent on a single TCP
>> connection without waiting for the corresponding responses. svn
>> lock/unlock uses HTTP pipelining to lock/unlock multiple files since
>> Subversion 1.9.0. HTTP pipelining is also used by 'svn checkout', but
>> this can be disabled on server or client-side.
>> I suggest you report this problem to Java-Tunnel developers.
> HTTP pipelining can only be disabled for 'svn checkout' and not for 'svn lock' ?
Yes, it only can be disabled for 'svn checkout'/'svn update', but not
for 'svn lock'/'svn unlock'. Actually there is no option to control
HTTP pipelining. There is an option to control what kind of protocol
to use for 'svn checkout'/'svn update' [1]. But essentially it
controls using HTTP pipelining, since only one protocol uses multiple
HTTP requests.

> Okay, great, this is a good hint to the problem. I will try to contact with the Java-Tunnel developers.
Please post results of your findings!

[1] https://subversion.apache.org/docs/release-notes/1.8.html#serf-skelta-default

Ivan Zhakov
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-05-09 15:12:25 CEST

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.