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

Re: BDB 4.4 + forking svnserve weirdness (issue 2564)

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2006-06-08 03:30:12 CEST

On Wed, 2006-06-07 at 14:57 -0400, Garrett Rooney wrote:
> Ok, so I figured that part out. The issue is pool
> creation/destruction ordering. The bdb environment cache is created
> after the connection pool, so it's destroyed before it (Last In, First
> Out). This means that by the time apr_terminate comes around and
> destroys the connection pool the bdb environment has already been
> paniced as part of the cache destruction process.

This feels like a problem best addressed in libsvn_fs_base, not in
svnserve. Why does destroying the environment cache pool first result
in a panicked environment?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 8 03:31:06 2006

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

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