SVN commit doesn't complete

When I commit files in svn I often get the situation where after it has transmitted all the files svn will hang and then eventually time out with the error svn: E175012: Connection timed out.

This seems to happen when I am uploading more than say 20 files.

  • What are some of the best SCM practices?
  • how do I work around this error while copying SVN repository by svnsync?
  • Migrating a directory to a different svn repository
  • How can I add a subversion history to GIT if the GIT is younger?
  • Structure of Projects in Version Control
  • How to skip first N commits when converting svn repo to Git using reposurgeon?
  • I believe this is happening after all of the files have been transferred to the server as either new periods will have stopped being added after Transmitting file data in the console, or all of the files have been listed as sent in Tortoise. Also, if I then do an update from the repository I get merges for all of the files I’ve just tried to commit (or, more annoyingly, a ton of conflicts to resolve) and when I then go to commit again there is nothing to commit – presumably meaning all of the files were successfully transmitted the first time.

    What could be causing this? It seems like the client is waiting for a ‘all done’ message from the server that is never arriving back at my PC?

    Our set up is TortoiseSVN 1.8.2 on the client and VisualSVN Server 2.7 on the server.

    I’ve checked for error messages in VisualSVN’s event log on the server and there aren’t any. This happens on both the office network and over VPN, and whether working on Wi-Fi or a wired connection.

  • how to use mercurial and svn together
  • svn command line from eclipse
  • Structure of Java web application?
  • Subversion in Intellij keeps asking for authentication
  • Cound not check out svn with xcode 5 and Xcode Crashes if enable svn
  • Which style do you use for your commit messages? Technical or feature-based?
  • One Solution collect form web for “SVN commit doesn't complete”

    It’s important to know how long it takes to commit revision’s data (time till transfer is complete and time till you get the timeout error.

    And don’t forget to check whether any post-commit hook script is processing your commits.

    If your commit contains some large files, then this error can be result of a mere timeout during data transmission. To troubleshoot the behavior, follow these steps:

    • Verify whether http-timeout is or not customized in %APPDATA%\Subversion\servers on the client. It makes sense to increase it’s value to 900 and see if the issue is solved.

    • If the above does not help, increase TimeOut on the server side.

      1. Open %VISUALSVN_SERVER%conf\httpd-custom.conf on the target server,
      2. Add the following line and save the file:

        TimeOut 900

      3. Stop-start cycle the VisualSVN Server instance.

      The documentation on the “TimeOut” directive can be found at

    Git Baby is a git and github fan, let's start git clone.