Ok. Just moving to log4j to avoid deprecation warning is not worth the
effort as we need to define a logging usage pattern and then move to it.
One big issue we have right now is that debug msgs are anything from
verbose one-time initialization mgs to per method traces of activity. The
server.log is inundated with output when any type of client throughput
is seen. For example, running the testsuite produces a 3Mb log file in
9 minutes.
I added a custom TRACE priority to allow finer granularity of debugging
msgs. The notion is that TRACE level msgs are those that are issued as a
result of some request while DEBUG msgs are not. We need to agree on
and formalize our logging convention and then move to it.
----- Original Message -----
From: "Chris Kimpton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 10, 2001 11:30 AM
Subject: Re: [JBoss-dev] log4j switchover - anyone working on this?
> Hi,
>
> --- Scott M Stark <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > I plan to look for code that has the correct logging and doing
> > > like-wise - so any recommendations?
> > What do you mean by changing "code that has the correct logging"?
> >
>
> umm, perhaps "correct" is the wrong phrase.
>
> I mean look for jboss code that is using log4j - I presume some is -
> and then use that as a model for making the non-log4j bits use
> log4j...
>
> Chris
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
