[please use plain-text formatting as documented in Community Guide [1]]
https://subversion.apache.org/docs/community-guide/mailing-lists.html#encodings
On 9 May 2016 at 12:05, Stefan Hett <stefan_at_egosoft.com> wrote:
>> On 5/9/2016 10:55 AM, Stefan Hett wrote:
>>> On 5/9/2016 10:09 AM, Ivan Zhakov wrote:
[...]
>>> Could you please provide reproduction script using command line
>>> client? As far I understand the problem in 'Java-SSL-Tunnel', not in
>>> Subversion itself.
>> I'll forward that to the user on the TSVN list, since I don't have any environment
>> at hand here to reproduce the described issue.
>
> Seems like I'm not fully awake yet... As far as I understood the issue, there's
> no way to reproduce the scenario just using the command line client, since
> that doesn't allow to lock multiple files over different paths (aka: there's no
> recursive-flag for svn lock).
>
'svn lock' accepts multiple targets:
$ svn lock a b c
'a' locked by user 'ivan'.
'b' locked by user 'ivan'.
'c' locked by user 'ivan'.
> The only way to reproduce the problem atm seems to be using some other
> client. In this particular case the issue is reported to be reproducible using
> TSVN 1.9.4 (which according to Stefan Küng uses the SVN API directly
> for the lock/unlock feature --- aka: I assume he's calling svn_ra_lock() by
> passing multiple path_revs - didn't check that, so take it with care).
>
> Do you have a lead for me how to get any further information from the user
> which would help to investigate the issue?
- RA layer is being used?
- Server-side Subversion version?
But most likely 'Java-SSL-Tunnel' acts as a 'busted proxy' and doesn't
handle HTTP pipelining properly. I assume users uses http:// protocol
to access the server. Switching to https:// may help in this case.
--
Ivan Zhakov
Received on 2016-05-09 12:32:06 CEST