[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Timeout on commit (Connection Closed Unexpectedly)

From: Troy Curtis Jr <troycurtisjr_at_gmail.com>
Date: 2007-03-26 05:13:38 CEST

Hi all,
At work several users have had their commit exit with the "Connection
Closed Unexpectedly" error message. Upon further investigation it
turns out that the commit makes it into the repository correctly, but
the working copy is left in such a screwed up state that they have to
do a fresh checkout to recover. (The working copy shows that the
commit failed and so does not update the version information for the
files commited, a 'svn up' causes conflicts galore). It also appears
that one particularly large text file (actually ridiculously large),
along with a generally large commit is common among the three case we
encountered (many other revs have gone through just fine).

Our repository is fairly large at ~2GB and 60k+ revisions.
Furthermore, our code tree is very complex with many many directories
at variable depths. We are using Subversion 1.4.1. The repository is
BDB back-end served off Subversion's own 'svnserve' server. I thought
I remembered something about the head revision re-write aspect of BDB
repos could cause timeouts on large commits but I couldn't find
anything on it.

Does anyone have any ideas? Would a transition to an Apache served
repository help?


"Beware of spyware. If you can, use the Firefox browser." - USA Today
Download now at http://getfirefox.com
Registered Linux User #354814 ( http://counter.li.org/)
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 26 05:14:06 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.