Looks like the context returned by AbstractLoggerAdapter.java:102 is the result of LogManager.getContext(someClass, false);
The boolean "false" indicates that a different LoggerContext may be created (and started). I suspect this is what causes the problem. Ralph understands this part better than me. Ralph, should the slf4j Log4jLoggerFactory pass "false" here? The default for LogManager seems to be "true"... Remko Sent from my iPhone > On 2015/07/21, at 22:58, Mikael Ståldal <[email protected]> wrote: > > AbstractLoggerAdapter.java:102 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
