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

Re: Commit error using 1.8.0 final

From: Lieven Govaerts <svnlgo_at_mobsol.be>
Date: Tue, 18 Jun 2013 08:57:22 +0200

On Tue, Jun 18, 2013 at 1:33 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Mon, Jun 17, 2013 at 4:00 PM, Lieven Govaerts <svnlgo_at_mobsol.be> wrote:
>> On Mon, Jun 17, 2013 at 9:22 PM, Mark Phippard <markphip_at_gmail.com> wrote:
>>> I updated my Windows laptop to 1.8.0 final. I am trying to commit a
>>> change for Subclipse to tigris.org and it is failing. The error
>>> message is not that helpful. Any ideas how to get better error
>>> information?
>>
>> There might be a higher level option, but in serf you can enable lots
>> of debug logging, at compile time in serf_private.h.
>> SSL_VERBOSE gives huge amount of log lines but is probably what you
>> need here, other interesting flags are SOCK_VERBOSE and CONN_VERBOSE.
>
> I sent Lieven a tcpdump. Hopefully that will help. In the meantime I
> found another tool that analyzes HTTP traffic. The last request
> before it fails is a DELETE request that the server responds with a
> 204. Would that be unexpected by Serf?

The DELETE is sent in the abort_edit callback (commit.c), so I suppose
that's in reaction of ra_serf receiving the error from serf when
reading the response.

> The URL for the DELETE request is:
>
> http://subclipse.tigris.org/svn/subclipse/!svn/act/b61b1e79-ba56-41b3-8b07-8649146e8212
>
> Right before that (maybe Serf has multiple connections going) is a

ra_serf uses only one serf connection in parallel for commit, but that
can manage multiple consecutive TCP connections.

> CHECKOUT that gets a 201. I notice that one says it was Closed by
> peer, so that might be the problem.

The error you see is SERF_ERROR_TRUNCATED_HTTP_RESPONSE. This is only
returned by serf in case of a response that's missing data, e.g. a
chunk that's too short or missing compressed bytes.

If the server closes the connection, it should have added the
"Connection: Close" header on the last response. Then serf will handle
this gracefully.

Lieven

> Here is the info I can get out of
> this tool:
>
> Request Headers:
>
> DAV: http://subversion.tigris.org/xmlns/dav/svn/depth,http://subversion.tigris.org/xmlns/dav/svn/mergeinfo,http://subversion.tigris.org/xmlns/dav/svn/log-revprops
> Transfer-Encoding: chunked
> User-Agent: SVN/1.8.0 (x86_64-apple-darwin11.4.2) serf/1.2.1
> Accept-Encoding: gzip
> Content-Type: text/xml
> Authorization: Basic xxxxxx
> Host: subclipse.tigris.org
>
> Response Headers:
>
> Server: Apache
> HelmLoginID: markphip
> Location: http://subclipse.tigris.org/svn/subclipse/!svn/wrk/b61b1e79-ba56-41b3-8b07-8649146e8212/trunk/www/update_1.10.x/features
> Cache-Control: no-cache
> Content-Type: text/html; charset=ISO-8859-1
> Content-Length: 349
> Date: Mon, 17 Jun 2013 23:22:39 GMT
>
> POST Text:
>
> <?xml version="1.0" encoding="utf-8"?><D:checkout
> xmlns:D="DAV:"><D:activity-set><D:href>/svn/subclipse/!svn/act/b61b1e79-ba56-41b3-8b07-8649146e8212</D:href></D:activity-set><D:apply-to-version></D:apply-to-version></D:checkout>
>
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
Received on 2013-06-18 08:58:23 CEST

This is an archived mail posted to the Subversion Dev mailing list.