logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Kemp" <mattk...@gmail.com>
Subject Re: Production configuration
Date Wed, 07 Nov 2007 15:00:17 GMT
Did you try setting the level of the root logger/all loggers to OFF?

On Nov 7, 2007 8:03 AM, Phillip Mills <pmills@systemcore.ca> wrote:

> For performance reasons, I would like to disable log4j logging entirely in
> a
> Java EE application, but I haven't stumbled on the magic formula yet.
> I've taken the approach of removing appenders from the <root> category and
> also tried explicit message suppression via the category priority
> configuration for things that are chatty.  The result is that I don't get
> output, but I am now seeing times when Category.getAppenders() is being
> called and, in fact, is the stack location for a number of BLOCKED threads
> (as described by a JBoss thread dump).  The offending log calls are not
> explicit in our code, but rather coming from 3rd-party things like Seam
> and
> Hibernate.
> What would be the most effective way to disable logging, and especially
> the
> locking overhead associated with finding out that there's no
> place/requirement to log?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message