On Thu, Jul 28, 2016 at 05:34:36PM +0200, Krzysztof Smiechowicz wrote: > W dniu 28.07.2016 o 10:01, Stefan Sperling pisze: > > My guess is that you need to increase the MaxKeepAliveRequests setting > > in httpd.conf on the SVN server. > > > > Once the MaxKeepAliveRequests limit is reached the server closes the > > connection so the client opens a new one and authenticates again. > > > > Serf-based clients send a lot more requests than Neon-based clients. > > It seems the Neon-based clients do not trigger the limit in your > > situations, while Serf-based clients do. > > > > Hello, > > Thank you for reply. We set this setting to 0 (unlimited),
That's OK for testing. In production you should set this to 10000. See the yellow box at: http://subversion.apache.org/docs/release-notes/1.8.html#neon-deleted > but the problem persists. Should this be entered into Subversion bugtracker? If, eventually, we come to agree that there is a bug, then filing an issue is a good idea, of course. But I still believe this can be explained by a server-side configuration problem, so I don't think filing a bug is necessary at this stage. Let's work some more on making sure keep-alives are configured correctly: Please ensure the KeepAlive directive is set to 'On'. http://httpd.apache.org/docs/2.4/mod/core.html#keepalive KeepAlive On And that the KeepAliveTimeout is set to at least 300 seconds: http://httpd.apache.org/docs/2.4/mod/core.html#keepalivetimeout KeepAliveTimeout 300 Does this help? If it does not, please share more details about your server-side authentication configuration in httpd.conf and related files. Thanks, Stefan
