> > > > I've tried with multiple repos of different sizes and ages. The > > > smaller repo I mentioned has about 150 files in trunk, mostly 50 KB > or > > > smaller, and about 500 revisions. A larger repo with the same > problems > > > has about 5000 files in trunk and 10,000 revisions. > > > > > > That *hints* at an httpd tuning issue, but I'm not sure. Check the > httpd > > > logs? > > > > The httpd logs show no signs of a problem. Success and failure cases > look the same in the logs. > > In your initial post your mentioned: > > >>> svn 1.10.2 was failing the same way before we upgraded to 1.14.1 as > a possible fix. > > So the problem isn't new after the upgrade.
Agreed. I see no change in behavior, good or bad, between SVN 1.10.2 and 1.14.1 for the many tests I've run. > BTW: as Daniel asked: You previously mentioned Subversion 1.14.1, is > that on the server or on the client? I've been testing with SVN 1.14.1 on both the client and server. > Regardless, since the issue manifests on the client-side by hangs and > crashes while waiting for / processing data from the server (hangs > inside libsvn_ra_serf), I'd suggest also to investigate whether there > is something in between your client and your server that might be > interfering. A proxy or reverse proxy perhaps? Or some security > software on the client that interferes with the network (as some > antivirus suites do on Windows)? If so, try to bypass it (or disable / > create an exclude rule), as a diagnostic step to see whether this > might be the cause. I don't think we have anything inserted between client and server, but will ask those smarter than me if they know of such a thing. I do have an update. My system administrator was surprised to see the server machine configured to support both version 4 and 6 IP addresses. He thought the latter were turned off. After that change, checkouts were noticeably faster, and hangs and crashes were noticeably less frequent. The repo size needed to trigger them appeared to grow some. Though a step forward, the configuration still isn't useable. It might also point at further network configuration problems as a cause, though the SVN client probably shouldn't crash in any case. Thanks for the reply. Jim
