directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lecharny <>
Subject Re: [jira] Commented: (DIREVE-171) add log4j config patch
Date Mon, 27 Jun 2005 06:51:27 GMT
> Is this really the recommended way of doing things? That means I can't easily 
> change the Level while the application is running.

It applies to debug, not to info. Whatever,not using it  it's not a big
deal, as using isDebugEnabled is good enough !

> Especially for a 24/7 server system as ApacheDS, this should be of special 
> concern, don't you think.

I don't think so, but I may be wrong. I do think that debug is for debug
purpose, when writing code (I mean, when in production, it's too late to
run in debug mode). So if you have a problem, you should isolate the
data that produce it, and then, debug it on a special environment,
setting the level to debug.

A few years ago, when working on a system that crashed in prod, I
suggested to put on the debug level. I got 2,5 Gb of logs in half an
hour. I can tell by experience (I spent hours reading those useless
lines of logs) that it does not help at all... 

Emmanuel L├ęcharny

View raw message