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

Concurrent access and "Delta source ended unexpectedly"

From: Philip Martin <pmartin_at_uklinux.net>
Date: 2001-11-06 15:20:39 CET


Looking through the code, subversion appears to lock the working copy
and the database, so working on the assumption that concurrent access
to a repository is supported, I tried testing using multiple clients
each in a separate working copy.

I have a couple of problems, one is that I can provoke deadlock
between the clients, the other is that I can provoke the following
error when trying to commit some changes:

  Sending wcstress.1617/bar2/foo1

  svn_error: #21006 : <Incomplete data>
    commit failed: wc locks have been removed.

  svn_error: #21006 : <Incomplete data>
    commit failed: while sending postfix text-deltas.

  svn_error: #21006 : <Incomplete data>
    Delta source ended unexpectedly

at which point the working copy seems to be broken.

My test is a script the invokes the Unix command line client, and it
works fine when I serialise the repository access. I am using
subversion revision 401, with apr, db and neon in the source tree, a
shared build and ra_local access.

Is it too early in development to expect concurrent access to work?

Is there anything special I need to do to enable concurrent access?

I will of course provide the script and instructions if this turns out
to be more than simply a configuration error on my part.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:48 2006

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