You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Alexandru Ioan Cucu <ai...@yahoo.com> on 2012/01/04 14:12:24 UTC
Commit failure when doing concurrent commits: "the specified activity does not exist"
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...)
Regards
Re: Commit failure when doing concurrent commits: "the specified activity does not exist"
Posted by Alexandru Ioan Cucu <ai...@yahoo.com>.
Yes, Thought that on the users mailing list there might be someone that might have had this problem many years ago :)
Thanks
________________________________
From: Andy Levy <an...@gmail.com>
To: Alexandru Ioan Cucu <ai...@yahoo.com>
Cc: "users@subversion.apache.org" <us...@subversion.apache.org>
Sent: Wednesday, January 4, 2012 5:13 PM
Subject: Re: Commit failure when doing concurrent commits: "the specified activity does not exist"
On Wed, Jan 4, 2012 at 08:12, Alexandru Ioan Cucu <ai...@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."
Re: Commit failure when doing concurrent commits: "the specified
activity does not exist"
Posted by Andy Levy <an...@gmail.com>.
On Wed, Jan 4, 2012 at 08:12, Alexandru Ioan Cucu <ai...@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."
Re: Commit failure when doing concurrent commits: "the specified
activity does not exist"
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Philip Martin wrote on Thu, Jan 05, 2012 at 01:12:23 +0000:
> Ryan Schmidt <su...@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".
Re: Commit failure when doing concurrent commits: "the specified activity does not exist"
Posted by Philip Martin <ph...@wandisco.com>.
Ryan Schmidt <su...@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.
--
Philip
Re: Commit failure when doing concurrent commits: "the specified activity does not exist"
Posted by Ryan Schmidt <su...@ryandesign.com>.
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.