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

Re: [Subclipse-users] "RA layer request failed" with long running commands

From: Mark Phippard <mphippard_at_collab.net>
Date: Fri, 23 Jan 2009 11:28:32 -0500

On Fri, Jan 23, 2009 at 11:19 AM, John J. Aylward <jaylward_at_cicat.com> wrote:
> With long running commands I get the following error:
>
> RA layer request failed
> svn: GET request failed: 400 Bad Request
>
> The server log indicates it's an error with the headers:
> [Fri Jan 23 11:04:31 2009] [error] [client ] request failed: error
> reading the headers
> [Fri Jan 23 11:04:32 2009] [error] [client ] request failed: error
> reading the headers
> [Fri Jan 23 11:04:32 2009] [error] [client ] request failed: error
> reading the headers
> [Fri Jan 23 11:04:34 2009] [error] [client ] Provider encountered an
> error while streaming a REPORT response. [500, #0]
> [Fri Jan 23 11:04:34 2009] [error] [client ] A failure occurred while
> driving the update report editor [500, #190004]
>
> What I noticed is that when using the command line version compiled with
> the serf DAV module I'd get the same error, but when I compiled SVN with
> neon as the DAV module everything worked fine.
>
> Would it be possible for the subclipse team to compile subclipse using
> the neon libs instead of serf for normal distribution? If not is there a
> way to let subclipse use the same libraries that the command line uses?

Subclipse Windows binaries include both and Neon would be used by
default. These are the same libraries as the command line.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=1045060
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-01-23 17:28:52 CET

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.