On 08/11/2007, at 2:18 AM, Phillip Mills wrote:
Thanks, I'll try. I hadn't discovered that as an option.
actually the most efficient way is to get the LoggerRepository object
and set that threshold to OFF. When deciding whether appenders get to
see an event, the LoggerRepository's thre
Thanks, I'll try. I hadn't discovered that as an option.
(Follow-up: Is there complete documentation or a DTD for log4j XML
configuration available?)
On 11/7/07, Matthew Kemp <[EMAIL PROTECTED]> wrote:
>
> Did you try setting the level of the root logger/all loggers to OFF?
>
> On Nov 7, 2007 8:
Did you try setting the level of the root logger/all loggers to OFF?
On Nov 7, 2007 8:03 AM, Phillip Mills <[EMAIL PROTECTED]> 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 t
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 category and
also tried explicit message suppression via the category priority
configuration fo
