On Wed, Nov 23, 2011 at 11:46 AM, Justin Johnson
<justinandtonya_at_gmail.com> wrote:
>>
>>> 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.
>
> http://wiki.wireshark.org/TCP%20ZeroWindow
>
> 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
> list.
For the record, we resolved the chunk size error by reconfiguring
Apache to use the prefork MPM instead of worker.
The base64 errors appear to be unrelated and only show up in log files.
Received on 2012-01-30 18:20:35 CET