Jira created https://issues.apache.org/jira/browse/LOG4J2-1094
On Thu, Aug 13, 2015 at 1:58 PM, Ralph Goers <[email protected]> wrote: > We are seeing your emails. The users list is just generally pretty quiet. > > Go ahead and create a Jira and attach something that will reproduce the > problem. > > Ralph > > > On Aug 13, 2015, at 12:09 AM, Xen <[email protected]> wrote: > > > > I get the same result from your code. Only thread-2 outputs something, > thread-1 comes before but the call comes up empty.: > > > > write thread-1 > > done thread-1 > > write thread-2 > > [TEST] [INFO ] thread-2 - message > > done thread-2 > > > > Any call to LogManager makes it succeed: > > > > LogManager.getContext(false); > > th1.start(); > > th2.start(); > > th1.join(); > > th2.join(); > > > > New output: > > > > write thread-2 > > write thread-1 > > [TEST] [INFO ] thread-2 - message > > done thread-2 > > [TEST] [INFO ] thread-1 - message > > done thread-1 > > > > The funny thing is that the first thread to arrive is initialized with > ERROR level instead of the ALL that is given to root. In other words it > seems that the config hasn't affectuated the root logger yet: > > > > write thread-1 to thread-1:ERROR in 1829164700 > > done thread-1 > > write thread-2 to thread-2:ALL in 1829164700 > > [TEST] [INFO ] thread-2 - message > > done thread-2 > > > > So when you increase our logging level in the calls:.... > > > > write thread-1 to thread-1:ERROR in 1829164700 > > 09:05:46.200 [Thread-0] ERROR thread-1 - message > > done thread-1 > > write thread-2 to thread-2:ALL in 1829164700 > > [TEST] [ERROR] thread-2 - message > > done thread-2 > > > > You also see that it still uses the old pattern, in other words the XML > hasn't been processed yet or taken affect. > > > > So the call proceeds but just acts on an uninitialized logger system. > > > > That's all I can do from here for now. Maybe better make Jira?. > > ---------------------- > > > > by the way is the list so defunct or have I been put on moderation? :P > :( :?. > > -------------- > > > > > > Hi, > > I have wrote a very simple example which has a behaviour I do not expect: > > > > If I call LogManager.getLogger(..) from two threads, only one of the > > loggers logs what I'd expect but if I add an additional call to > > LogManager.getLogger(..) before the threads are started, I see what I'd > > expect so it looks like there is a problem in multi threaded > initialization. > > > > You can fine the code and the configuration here: > > > > - > > > https://github.com/lburgazzoli/lb-chronicle/blob/master/chronicle-examples/chronicle-logger-log4j2/src/main/java/com.github.lburgazzoli.openhft.examples.chronicle.logger.log4j2/MtLogging.java > > - > > > https://github.com/lburgazzoli/lb-chronicle/blob/master/chronicle-examples/chronicle-logger-log4j2/src/main/resources/log4j2.xml > > > > Am I doing something wrong ? > > > > Regards, > > Luca > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
