https://bz.apache.org/bugzilla/show_bug.cgi?id=63503
--- Comment #7 from Ruediger Pluem <[email protected]> --- (In reply to Don Poitras from comment #0) > > Looking at these new core files, it could be seen that two threads were > concurrently accessing the same worker proxy connection pool. While > proxy_util.c has one mutex call around the call to apr_sockaddr_info_get() > (where the proxy connection pool is used), there were other calls in this > module that needed the same protection. I know I am late with this, but can you please provide the stack traces of both threads that access the pool concurrently? I think the solution you provide creates too much locking overhead, but knowing where it clashes could be helpful to propose an alternative solution. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
