[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: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 4 Jan 2012 10:13:45 -0500

On Wed, Jan 4, 2012 at 08:12, Alexandru Ioan Cucu <ai_cucu_at_yahoo.com> wrote:
> Hello guys,
>
> I'm running the following configuration:
>
> OS:  Ubuntu 8.04 (Hardy Heron)
> svn: 1.4.6dfsg1-2ubuntu1.3
> apache2: 2.2.8-1ubuntu0.22
> apache2-mpm-prefork: 2.2.8-1ubuntu0.22
>
> And experiencing the following problem:
> When performing simultaneous commits from 5 different stations, some commits
> fail with the following messages (taken from the apache error log):
>
> [Wed Dec 14 09:59:20 2011] [error] [client 10.46.1.21] Could not CHECKOUT
> resource /cp1-svn/!svn/bln/17472.  [409, #0]
> [Wed Dec 14 09:59:20 2011] [error] [client 10.46.1.21] The specified
> activity does not exist.  [409, #190002]
>
> 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...)

Subversion 1.4 is no longer supported (and that has been the case for
a very long time), so unless you're looking to perform your own fix to
the source, the first response you're going to get is "upgrade to a
supported release."
Received on 2012-01-04 16:15:00 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.