The link I provided is *exactly* what I'm seeing, so I didn't see the need to repeat that post. I'm in a VM, the client drops the connection with an erroneous [FIN, ACK], just after the TCP window opens up again.
Hm, one detail I can provide now that's not in that post: U directory/file1 U directory/file2 svn: E175002: REPORT of '/svn/repos/<name>/!svn/me': Could not read response body: connection was closed by server (http://<server>) I don't know what's on the server side, and may not be able to find out, but I'll inquire. Hm, actually the network trace shows "Server: nginx/1.0.5". Client operation is 'svn up'. What else would you like me to do/provide? ...Stu On Mon, Dec 16, 2013 at 12:05 PM, Ben Reser <b...@reser.org> wrote: > On Mon Dec 16 07:56:32 2013, Stuart MacDonald wrote: > > > > I am seeing exactly this > > issue: > https://groups.google.com/forum/#!topic/subversion_users/AZ4M62Qwmjc > > but do not find a bug report for it in the database. The linked bug is > for > > something similar but unrelated. Can I file this? > > > > ...Stu > > > > stumacdonald@stumacdonald-VirtualBox:~/src/ianywhere$ svn --version > > svn, version 1.7.13 (r1516569) > > compiled Aug 27 2013, 09:06:07 > > > > Copyright (C) 2013 The Apache Software Foundation. > > This software consists of contributions made by many people; see the > NOTICE > > file for more information. > > Subversion is open source software, see http://subversion.apache.org/ > > > > The following repository access (RA) modules are available: > > > > * ra_neon : Module for accessing a repository via WebDAV protocol using > Neon. > > - handles 'http' scheme > > - handles 'https' scheme > > * ra_svn : Module for accessing a repository using the svn network > protocol. > > - with Cyrus SASL authentication > > - handles 'svn' scheme > > * ra_local : Module for accessing a repository on local disk. > > - handles 'file' scheme > > Before reporting an issue you really ought to try it with the most > recent version of Subversion (1.7.14 and 1.8.5). Since 1.8.0 we only > use the serf http-library. If you can trigger the same issue with > 1.8.5 then that's likely a sign that we aren't tending the TCP > connections as we should (vs the neon http library that your version > output shows you're using with 1.7.13). Another point is that you > really should provide more details here. What versions of httpd and > svn are on the server side? What client operation(s) are you having > the issue with. > > Without a lot more research on your part the bug isn't likely to get > much interest. >
