Thanks Ceki, that was it.. I had tried this, but in the wrong place (the code that configures Chainsaw when it's started as an appender).
-----Original Message----- From: Ceki Gülcü [mailto:[EMAIL PROTECTED] Sent: Wed 12/1/2004 2:05 AM To: Log4J Developers List Cc: Subject: Re: Log4j-1.3 root logger default to trace? Scott, At 08:51 AM 12/1/2004, you wrote: >I'm trying to enable TRACE support in Chainsaw. > >The logManager's static block creates a defaultHierarchy with a rootLogger >whose level is DEBUG, not ALL or TRACE. > >In my attempts to set the level to TRACE, nothing has worked. > >My questions: >1. Should the level of logmanager's defaultHierarchy be ALL or TRACE? > My vote is for ALL. No, leave it as is. >2. Should both loggerrepository.setThreshold methods be deprecated? Yes, they should be deprecated. We'll get to that in due time. >3. What is the functional equivalent of setThreshold? Look at the source code for the first lines of any printing method, Logger.trace(), Logger.debug(), etc. >4. Is setThreshold what I should be calling in order to programmatically > change the root logger's level to TRACE in Chainsaw? > This didn't work: > LogManager.getRepositorySelector().getDefaultRepository(). > setThreshold(Level.TRACE); No, try: LogManager.getRootLogger().setLevel(Level.TRACE)? >Thanks > >Scott -- Ceki Gülcü The complete log4j manual: http://qos.ch/eclm Professional log4j support: http://qos.ch/log4jSupport --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
<<winmail.dat>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
