On 8/19/06, Rob Wilkerson <r.d.wilkerson@gmail.com> wrote:
> Can someone help me understand why I can't seem to perform large-scale
> commits? Is this a limitation of Subversion? I have a reasonably
> large - but not crazy - repository (roughly 3,000 files). I just set
> svn:keywords on all files from the root and that worked great. When I
> try to commit, however, the commit fails. If I try the same commit
> multiple times, the reason for the failure changes frequently. The
> "location" of the error (at least where it's reported in the commit
> process) changes every single time.
>
> Sometimes I get this:
> At least one property change failed; repository is unchanged
>
> Sometimes I get this:
> CHECKOUT of '/repos/myproject/!svn/ver/16/branches/dev/tahoe-code-reorg/.java/src/com/wintertree/ssce/PropSpellingSession.java':
> could not connect to server (http://vm-seprojects)
>
> There are one or two others that make an appearance, too, but I don't
> have access to those at the moment. Considering the inconsistency
> with which I get them and the locations in which they're reported, the
> message itself may (or may not) be terribly important.
>
> Seems like doing several smaller commits solves the problem, but
> that's not really much of a solution.
>
> This has happened to me before on large commits and I've never been
> able to figure it out. Anyone have any thoughts?
The Apache server has a maximum XML request body. If you surpass the
amount specified, the server hangs up the connection. In the second
case, you may have hit that problem. Search the Apache docs for the
parameter to set.
In the former case, you may have hit a bdb locks limit, if your
repository is bdb; you can change the DB_CONFIG file to up the limit
of available locks.
HTH,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 21 12:37:06 2006