On Tue, May 15, 2012 at 11:10:35AM +0800, Joel Low wrote:
> I was doing a switch for my Apache HTTPd WC from the 2.2 tag to the latest
> 2.4 tag in preparation for building 1.7.5's mod_dav_svn. I am using Serf as
> the RA layer: after a minute or two I get the message in the title; I don't
> get the problem using Neon. I've already done a Wireshark capture, so let me
> know who to email it to if it would help debugging.
> I think I need to disclaim that I am connected to s.a.o from Singapore,
> where there is a transparent HTTP proxy implemented at the national level
> for all HTTP requests being routed out of the country. It could be that
> causing the misbehaviour with Serf.
> Thanks in advance.
There are and were many known problems with the serf-based repository
access layer, which is why neon is still the default in Subversion 1.7.
There is work happening on trunk at the moment to iron out these problems.
If you report problems with serf, you should mention the exact version
numbers of serf and Subversion you used. Else, it is hard to tell whether
you ran into some problem that's already been fixed.
If you're in a position to try an svn client compiled from Subversion's
trunk, and linked against the most recent stable release of serf, that
would be help us identify problems that still need to be fixed before
serf can be made the default for Subversion 1.8.
Received on 2012-05-15 11:12:15 CEST