@ceki I just ran into this issue as well (LOGBACK-1454); I agree that the root cause is the application (the circular exception). But it really hurts the ability to find the mistake if the logging framework swallows the exception and causes an error of its own. This is particularly true the root cause it only occurs sporadically and in production, where you may only have access to logs and not be able to attach a debugger.

I see that there is a PR open for this since 2017. Any concerns with it, or plans to merge it? If there is anything that I could help with to get the PR accepted, I would be happy to contribute as well.