I worked with Philip today and was able to reproduce the exact problem
he's been seeing. I ended up having to get his full httpd.conf to
figure it out..
Ultimately the problem proved to be that he had this directive:
Timeout 3
Which would mean if we don't tend a connection for 3 seconds Apache
will close it. Serf should be able to deal with the connection being
closed.
So we'll need to do some further investigation. However, it should be
possible to replicate this easier now by setting a lower Timeout.
On Mon, Nov 5, 2012 at 5:17 PM, Philip Martin
<philip.martin_at_wandisco.com> wrote:
> Lieven Govaerts <lgo_at_mobsol.be> writes:
>
>> From your previous report I noticed the 406 response that serf isn't
>> handling, at least serf doesn't support a response coming in while the
>> matching request wasn't completely sent yet. I guess that 406 response
>> was for a REPORT request not flushed fast enough.
>
> In case it makes a difference I'm using the worker MPM configured:
>
> KeepAlive On
> StartServers 1
> MaxClients 8
> MinSpareThreads 2
> MaxSpareThreads 8
> ThreadsPerChild 8
> MaxRequestsPerChild 0
> MaxKeepAliveRequests 100
>
> so all requests are handled by threads in the same process.
>
> --
> Certified & Supported Apache Subversion Downloads:
> http://www.wandisco.com/subversion/download
Received on 2012-11-06 16:10:16 CET