Github user cakofony commented on the issue:
https://github.com/apache/logging-log4j2/pull/206
@kmeurer I would recommend that you create a forked build to run with in
production for a bit before cutting an official release here. That will likely
tease out a few issues without being tied to the log4j release cycle.---
