On Mon, Feb 20, 2017 at 10:48 PM, Yann Ylavic <ylavic....@gmail.com> wrote: > > The hard thing is that at the time ptrans is created, we don't know > how it will be used. > Maybe we could differ apr_allocator_mutex_set() at a later time, e.g. > {pre,process}_connection hook?
Theorically though, a module that creates multiple threads and ptrans' subpools to handle a connection shouldn't necessarily have to deal with this, that's mpm_event which first created/changed the allocator to something non thread-safe...