A note about mod_shib2 and mod_http2

[Cantor, Scott]

> But there's nothing there that looks unusual. There are several of those threads
> in any system running Shibboleth and they'll all be waiting on condition
> variables in an idle state most of the time. There is no reason to imagine they
> are hung up, nor would they be consuming CPU.

(And to be clear if you're saying those exact stack traces were from threads consuming CPU, that doesn't seem possible, they appeared to be waiting on a mutex, not performing a system call that would be chewing cycles.)

-- Scott