logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacob Kjome <h...@visi.com>
Subject Re: simple log4j.properties question on excluding classes
Date Sat, 16 May 2009 01:10:05 GMT
On 5/15/2009 1:06 PM, Jason Novotny wrote:
> Hi,
> 
> Typically I have a setup like:
> 
> log4j.rootLogger=ERROR, console, file
> ...
> log4j.logger.com.mypackage=DEBUG
> 
> 
> but then classes in com.mypackage are not logged in debug since
> rootLogger is ERROR.

Classes in com.mypackage should most assuredly be logged at the level of DEBUG
given your configuration above.  If you are not experiencing this, then there is
something wrong.  Try setting -Dlog4j.debug=true to verify that the config file
you think is being used is actually being used.  For instance, if there were a
log4j.xml in the classpath, it would get used in preference to log4j.propeties

BTW, I recommend setting the rootLogger to the level of WARN, not ERROR.  Surely
you are interested in seeing WARN message from any logger, no matter the origin.


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


Mime
View raw message