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

Re: Commit failure when doing concurrent commits: "the specified activity does not exist"

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Thu, 5 Jan 2012 03:34:59 +0200

Philip Martin wrote on Thu, Jan 05, 2012 at 01:12:23 +0000:
> Ryan Schmidt <subversion-2012a_at_ryandesign.com> writes:
>
> > On Jan 4, 2012, at 07:12, Alexandru Ioan Cucu wrote:
> >
> >> I've been browsing through the 1.4.6 subversion sources and noticed
> >> that this error message is given when apr_dbm_open or apr_dbm_fetch
> >> fail for any reason (look in mod_dav_svn/activity.c --> const char
> >> *dav_svn_get_txn) so I would assume this is caused by concurrency
> >> issues in Berkley DB or in APR... (though this is just an
> >> assumption...)
> >
> > Also, if you are indeed using a BerkeleyDB-based repository, I'd
> > suggest a dump/load cycle to get onto an FSFS-based repository so you
> > can avoid all the BDB-specific problems. FSFS has been the default
> > repository type since Subversion 1.2 IIRC.
>
> In 1.5 Subversion stopped using the apr_dbm API for the activities
> database and uses a simple MD5 filename system instead, and the v2
> protocol in 1.7 usually bypasses the activities database altogether.

AKA: "this is a use of BDB within mod_dav_svn 1.4 and earlier, and is
not the same thing as whether the libsvn_fs backend is FSFS or BDB".
Received on 2012-01-05 02:35:41 CET

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.