[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-httpd-bugs
Subject:    [Bug 53870] Deadlock in CRYPTO_add_lock with Apache 2.2.22 worker MPM on Solaris 9 64-bit
From:       bugzilla () apache ! org
Date:       2012-11-28 21:30:16
Message-ID: bug-53870-7868-xc14flLS4K () https ! issues ! apache ! org/bugzilla/
[Download RAW message or body]

https://issues.apache.org/bugzilla/show_bug.cgi?id=53870

Daniel Ruggeri <DRuggeri@primary.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |DRuggeri@primary.net

--- Comment #8 from Daniel Ruggeri <DRuggeri@primary.net> ---
For those seeing the issue: Are you using an engine (SSLCryptoDevice)? I know
some register their own callbacks for locks - not sure if that's coming into
play.





I see similar behavior as well on Solaris 10 w/ worker in openssl-0.9.8u, but
far fewer zombie processes. This is on a particularly busy production install
rather than under a load test scenario. Just like the original bug, I see a few
threads interacting with a proxied resource with most threads sitting in
CRYPTO_add_lock. There is at least one zombie thread in 5 of the 6 running
child processes. The child process without any zombies are still sitting in
CRYPTO_add_lock.


I can attach pstack output as well, but the short version is:
*Very few threads doing work
*Many threads waiting in CRYPTO_add_lock
*Did not seem to happen in 2.2.13 w/ openssl-0.9.8l with an otherwise identical
config


Happy to provide more info if needed

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]