You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2022/07/11 07:27:27 UTC

[Bug 66160] Apache HTTPD stops serving and freezes HTTP/2 connections

https://bz.apache.org/bugzilla/show_bug.cgi?id=66160

--- Comment #1 from Stefan Eissing <ic...@apache.org> ---
Hi Steffen,

the stacktrace you listed does not point to a deadlock. The conditional, timed
wait release the mutex. So it cannot be blocking others. If someone is holding
the mplx lock, it must be another thread.

Seeing h2 in this part of code is expected during connection processing. The
question is if your apache stops serving new connections or new requests on
existing connections. The former would point to an exhaustion of the mpm
workers, the latter to an exhaustion of the h2 worker pool.

Exhaustion can happen due to insufficient capacity or indeed a bug in the
server that blocks processing and holds resources too long.

The most tricky things in a HTTP server are long running requests. If your
setup/backend possibly encounters those, they can clog up your system. HTTP/2
is more vulnerable to that, if your h2 worker pool is "too small".

Hope this helps,

Stefan

-- 
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