yep ... that did the trick for me as well ... turned keepalive back on
and http-compression off client-side ... works like a charm now
thanks!
> -----Original Message-----
> From: Nicklas Norling [mailto:nicklas.norling@ifsab.se]
> Sent: Tuesday, June 29, 2004 4:45 AM
> To: 'Rob van Oostrum'; Klaus Rennecke
> Cc: users@subversion.tigris.org
> Subject: RE: large checkout/update/switch fails (svn: The
> REPORT request
> r eturned invalid XML in response)
>
>
> This all sounds very similar ta what I have repoted when turning
> on compression. I get pretty much the exact same thing. Turning
> compression off I have no more XML errors, never fiddled around
> with keep alives.
>
> Could this be the same issue, or are these two issues touching
> common code where a bug is lurking?
>
> I never did receive much feedback from my emails. I had to resort
> to disabling http-compression to get things to work. It was reliably
> and repetably stopping with this error everytime even on different
> servers. Had to use win32 client.
>
> /Nicke
>
> > -----Original Message-----
> > From: Rob van Oostrum [mailto:rob.vanoostrum@blastradius.com]
> > Sent: den 28 juni 2004 17:58
> > To: Klaus Rennecke
> > Cc: users@subversion.tigris.org
> > Subject: RE: large checkout/update/switch fails (svn: The
> > REPORT request returned invalid XML in response)
> >
> >
> > Yeah that's what I figure ... after some more testing the
> > problem popped up again, and I'm essentially back to square
> > one. Pretty average Monday morning so far ;-)
> >
> >
> > > -----Original Message-----
> > > From: Klaus Rennecke [mailto:kre@tigris.org]
> > > Sent: Monday, June 28, 2004 11:41 AM
> > > To: Rob van Oostrum
> > > Cc: users@subversion.tigris.org
> > > Subject: Re: large checkout/update/switch fails (svn: The
> > > REPORT request
> > > returned invalid XML in response)
> > >
> > >
> > > Rob van Oostrum wrote:
> > >
> > > >Ok, so I did some tweaking and found a workaround that will
> > > keep me in
> > > >business for the time being.
> > > >
> > > >I tried setting MaxKeepAliveRequests to 0, and it got a lot
> > > farther than
> > > >before, but it now found a new point to consistently crap
> > > out at (same
> > > >error). So ... I turned off KeepAlive altogether, and that
> > > seems to do
> > > >the trick. I'm sure it's going to get me in trouble with
> > scalability,
> > > >but that's a worry for another day. Do you think it would
> > > make sense to
> > > >open a bug for this and I'll attach information when I have
> > > tim eto do
> > > >some more investigation on the matter?
> > > >[...]
> > > >
> > > >
> > >
> > > IANAD (... Not A Developer), but to me this smells pretty
> > > strong like an
> > > issue. At the very least, a prominent notice in the documentation.
> > >
> > > /Klaus
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 29 17:57:10 2004