>>> On 3/16/2006 at 7:01 pm, in message <[EMAIL PROTECTED]>, "Jeff Trawick" <[EMAIL PROTECTED]> wrote: > On 3/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >> URL: http://svn.apache.org/viewcvs?rev=386477&view=rev >> Log: >> remove the race condition when creating the connection pool mutex. Also > eliminate some unnecessary uses of the global memory pool > > cool! > >> @@ -1753,7 +1753,10 @@ >> util_ldap_state_t *base = (util_ldap_state_t *) basev; >> util_ldap_state_t *overrides = (util_ldap_state_t *) overridesv; >> >> - st->pool = p; >> + st->pool = base->pool; >> +#if APR_HAS_THREADS >> + st->mutex = base->mutex; >> +#endif > > What this use of the base pool and mutex means is that while a subpool > and mutex were created for the vhost, we'll never use them. Instead, > we'll use the subpool and mutex created for the main server. > > Not what you meant, right
I guess I don't understand. When I tested this using the worker MPM (3 servers, 25 threads each) and configuring both an ldap protected directory in the main server and an ldap protected directory in a vhost, it never had a problem locking the mutex or allocating memory. Am I missing something? Brad
