[Bug 63024] New: pthread mutexes are leaking?
Bug ID: 63024
Summary: pthread mutexes are leaking?
Product: Apache httpd-2
Target Milestone: ---
Using the Weblogic Webserver plugin as a proxy module to the Weblogic Webserver
plugin, we frequently see the following error in the logs, from the module.
Mon Dec 17 08:24:13.857204 2018] [weblogic:error] [pid 3241716:tid
140206280066816] [client 220.127.116.11:0] couldn't acquire p_lock
[Mon Dec 17 08:24:13.857238 2018] [weblogic:error] [pid 3241716:tid
140206280066816] [client 18.104.22.168:0] <3241716154503505326814>
*******Exception type [NO_RESOURCES] (countn't acquire p_lock) raised at line
2872 of ApacheProxy.cpp
[Mon Dec 17 08:24:13.857314 2018] [weblogic:error] [pid 3241716:tid
140206280066816] [client 22.214.171.124:0] ap_proxy: trying GET
/<redacted>/!@8ec1ade37d9b45a9e45d9d0c5a7c3618! at backend host
126.96.36.199/24101; got exception 'NO_RESOURCES: [os error=115, line 2872 of
ApacheProxy.cpp]: countn't acquire p_lock'; state: preparing request headers
(wrote? N read? N); not failing over
Oracle have fixed this error in their OHS (Oracle HTTPD server) which is a fork
of Apache (presumably 2.4) with the following reference.
and the following cryptic note:
"There was an issue attaching the process lock to each child thread this has
been corrected by the following bug:
Bug 28214157 - OHS STOPS PROCESSING WEBSOCKET REQUESTS WITH ERROR (COUNTN'T
This fix was published very recently, 5 Nov 2018. Now that we are facing this
problem, the Oracle support team are suggesting the Apache maintainers will
need to apply this same fix. Unfortunately, I don't know what it is in any
This error is characteristic of a pthread mutex leak, acquiring another lock on
the same mutex with each thread entry. A little test C program shows that this
error is only achieved if the same mutex is locked 2^32-1 times and then once
more, so clearly there's a 32-bit integer tracking locks.
I honestly cannot tell is this leak is in the plugin or in the apache core. It
seems more reasonable to assume the leak is in the plugin, but Oracle support
have directed me to the Apache maintainers. I will attempt to clarify where
they did the fix, but I thought I would raise this issue here as well for
information, if nothing else.
You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail: bugs-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: bugs-help@xxxxxxxxxxxxxxxx