Yes, there is an example in the default log4j.properties file that is
commented
out. Simply uncomment the last line as follows:
# An example of enabling the custom TRACE level priority that is used
# by the JBoss internals to diagnose low level details. This example
# turns on TRACE level msgs for the org.jboss.ejb.plugins package and its
# subpackages. This will produce A LOT of logging output.
log4j.category.org.jboss.ejb.plugins=TRACE#org.jboss.logging.log4j.TracePrio
rity
If you now invoke an ejb method you will see a large number of messages
detailing
the activity of the Entity instance locking for example(provided that was
not dropped
in the RH changes).
Before rushing off to switch to using this custom priority however, I would
like
to have an agreement that is the best way to do this.
----- Original Message -----
From: "David Jencks" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 10, 2001 12:54 PM
Subject: Re: [JBoss-dev] log4j switchover - anyone working on this?
> Hi,
> So far I have been unsuccessful in turning on the TRACE priority -- thus
> the excessive DEBUG stuff I have been using. Do you have an example of
how
> to turn it on? If I can get it to work I will happily turn most of my
> debugs into traces.
>
> Thanks
> david jencks
>
> On 2001.09.10 15:12:06 -0400 Scott M Stark wrote:
> > 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.
> >
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
