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

Re: Could not read chunk size: connection was closed by server

From: Justin Johnson <justinandtonya_at_gmail.com>
Date: Wed, 23 Nov 2011 11:46:55 -0600

>> during a checkout.
>>   Could not read chunk size: connection was closed by server
>> In the server logs the following errors appear around the same time.
>>   Provider encountered an error while streaming a REPORT response.  [500, #0]
>>   A failure occurred while driving the update report editor  [500, #130]
>>   Error writing base64 data: Software caused connection abort  [500, #130]
> The server failed to write to the client and the client failed to read
> from the server.  Looks like a network problem caused the connection to
> be shut down.  To diagnose it you probably need to capture a network
> trace of some sort.

What we've seen is that normal behavior is to have numerous TCP Zero
Window flags occur during a checkout.


Occasionally we get the errors above and the Wireshark capture
indicates the Subversion server eventually just terminates the
connection. I can gather more details if it would be helpful, but I
won't be able to include all of the capture details on his mailing
Received on 2011-11-23 18:47:27 CET

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

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