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

> >> This could happen for three reasons:
> >> 1. The file is already locked before executing 'svn lock'.
> >> 2. 'Java SSL Tunnel' mixes-up HTTP requests and send one LOCK request
> >> multiple times.
> >> 3. There is bug in ra_serf/serf and it sends the same requests more
> >> than once in some circumstances.
> >>
> >> I assume that you're using clean repository for tests, so (1) is not
> >> likely the case. Bug in ra_serf/serf (3) is also possible, but I don't
> >> think it's very likely since issue doesn't trigger when accessing
> >> server directly. So in my opinion it's problem in Java SSL Tunnel (2).
> >> HTTP proxies/filters known to be working really bad with HTTP
> >> pipelining.
> > Yes, a clean repository was used.
> >
> > If http proxies are known to work really bad with http pipelining it might be a nice svn-feature to switch pipelining on and off?
> Given that SVN 1.9 is already out for several months and your report is
> the first one which seems to be related to some http pipelining
> problems, I wouldn't draw the conclusion that http proxies are in
> general known to work bad with http pipelining. Do you have any other
> reason to come to that conclusion?

This (general) statement was taken from Ivans answer. Maybe he has some more details about this topic?

Correct, it might be that the Java-Tunnel used in my case is quite particular and does not provide or badly implements http pipelining.

Besides it seems to be a propriatory development from one of our service providers and it seems quite difficult to contact the developers. So in my case I will stay with svn <1.9.0 for the moment and test again in some months.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3171846

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-05-10 15:20:56 CEST