Aha! Thank you! Sent from my iPhone
> On 2014/06/16, at 1:12, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > That happens because line 51 is > > ((LifeCycle) LogManager.getContext()).stop(); // stop async thread > > and should be > > ((LifeCycle) LogManager.getContext(false)).stop(); // stop async thread > > Ralph > >> On Jun 15, 2014, at 12:16 AM, Remko Popma <remko.po...@gmail.com> wrote: >> >> After improving the status logging, it is now clear that there are two >> LoggerContexts started: >> one with name=sun.misc.Launcher$AppClassLoader@1f3e8d89, and >> one with name=Default >> >> Is this expected? >> >> To reproduce this, change <Configuration status="OFF"... to status="TRACE" >> in /log4j-core/src/test/resources/XmlCompleteFileAppenderTest.xml >> and run >> /log4j-core/src/test/java/org/apache/logging/log4j/core/appender/XmlCompleteFileAppenderTest.java >> >> and see the status log. >> >> It looks strange, I would expect only one context, no? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-dev-h...@logging.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
