idp.loglevel.idp DEBUG in production - 100% CPU usage

Tue Mar 6 13:57:32 EST 2018

Under v3.3.2 when I set idp.loglevel.idp to DEBUG in logback.xml (on a production server with about 84k sessions per day) and reload the configuration the cpu usage for the java process immediately spikes from ~5% to 100% and the whole framework collapses with timeouts to AJP, etc... I don't recall this behavior under v2. Enabling DEBUG in production is rare but is sometimes needed. None of the other Logging Level shortcuts have this effect. Should I report this as a bug and if so where?

---
Roberto Ullfig - rullfig at uic.edu
Systems Administrator
Enterprise Architecture and Development | ACCC
University of Illinois - Chicago

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180306/52537ed9/attachment.html>