At 01:58 AM 9/4/2006, you wrote: >From: Curt Arnold [mailto:[EMAIL PROTECTED] > >> Things particularly get >> interesting in configuration as log messages are cached until the >> configuration is complete and then replayed through the newly >> configured logging hierarchy. That additivity doesn't work as >> expected in that scenario. > >Thanks for the explanation, it clears up a lot. However, although it >explains that I see log messages in places I don't expect them with the >additivity settings I have, it does not explain that I can also see the >additivity still (or again) set to true by *explicitly* reading it from >the log4j logger with the getAdditivity() method. Am I using the wrong >method of retrieving the org.apache.log4j Logger - >Logger.getLogger("org.apache.log4j")? >
Additivity is enabled by default. And why would you want to obtain the "org.apache.log4j" logger? Certainly you don't want to log to it. Log4j is the only library with any business logging to that logger.
Jake >Best regards, > >Eelke Blok > > >--------------------------------------------------------------------- >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]
