On 6/7/06, David Anderson <david.anderson@calixo.net> wrote:
> * Garrett Rooney <rooneg@electricjellyfish.net> [2006-06-07 14:57:50]:
> > 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.
>
> Obscure. Thanks for tracking this down!
>
> I agree with you that it is not only "nice", but vital for our tests
> to work. So, +1 on the pool destruction change. Please do put a
> comment around that area explaining what the bug is caused by, and the
> rationale behind forcing pool destruction.
Committed in r19992. Will propose for backport now.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 7 21:18:59 2006