A note about mod_shib2 and mod_http2

Jacob Lundberg jacob at collegenet.com
Thu Mar 8 16:40:27 EST 2018

Hi Scott,

I had to pull some monitoring reports from 2017 but yes we originally
saw CPU utilization step up in whole number increments just like it is
in our testing now.  In other words, if our problem was ever CPPXT-116,
there is no reason to think it isn't still CPPXT-116.  FWIW at that time
I provided debug info in #httpd-dev and they agreed I was having
deadlocks in SP code, which is why we assumed it was CPPXT-116.

All of the httpd processes with high load have pairs of threads which
appear to be stuck in the xmltooling locking code path I provided in the
previous message.  At least, I haven't managed to catch them in any
other code path and the thread IDs remain the same.


On Thu, 2018-03-08 at 03:25 +0000, Cantor, Scott wrote:
> I don't really think this has anything to do with the original bug or
> the patch. Nothing in that code would cause the CPU to be tied up. A
> deadlock would be idle and I'm sure the original bug was manifesting
> that way, though I never saw it happen. This can't be that bug.
> -- Scott


Jacob Lundberg
AVP, IT Architecture
503.290.0100 (voice)
503.973.5252 (fax)

More information about the users mailing list