Just wondering if we can get some advice on this issue as it has become a head scratcher.
All in house tools create a mutex lock around all svn commands named with the root path of the working copy. (This gets around multiple updates/commits being no longer supported in 1.7 command line, allowing multiple threads and applications to use the same repo). We also sleep within the mutex for 20 milliseconds after the svn process has been killed off. Even with all of the precautions above on a single multi threaded application we see the error below on average seven times in two thousand individual updates. svn: E155004: Working copy '*' locked svn: E200033: database is locked svn: E200033: database is locked svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) We are using the command line “CollabNet Subversion Client 1.7.0.4 x64.exe”. While searching this seems similar to the “1.7.1: E200033: database is locked, executing statement 'RELEASE s0'” thread back in November. I can confirm we are definatly not calling svn.exe multiple times due to the mutex and sleep. Before we added the sleep this error was more frequent, I don’t suppose the svn.exe does post processing via an external process that keeps the database locked? Thanks in advance -Adrian
