I agree that fixing the root cause of a circular dependency should be the ultimate goal, but sometimes this isn't possible as you might not be able to change that code.

On the other hand, knowing that logback might suffer from such an exception doesn't really give confidence, as you might never know when such an exception comes along. Knowing that logback can handle such a scenario properly would definitely help.

For me this boils down to two options right now, finding every cause for such an exception in the other code, wrapping those exceptions in my own. Or simply switching aware from logback.

I am really a fan of logback and would really like to see this fixed!