-
1. Re: Verbose JBoss Logging
adrian.brock Jan 4, 2002 2:59 PM (in response to neut6o1)Hi,
Rather than changing the appender threshold,
you can change the categories individually.
log4j.category.org.jboss=WARN
This will still show the started message
because it doesn't go to an org.jboss category.
You can control each category individually.
To see the full category names
change the conversion pattern to [%c] instead of
[%c{1}] which only shows the last part.
Regards,
Adrian -
2. Re: Verbose JBoss Logging
neut6o1 Jan 4, 2002 4:14 PM (in response to neut6o1)Thanks warjort, for your help. It worked very well. I now have the exact amount of logging that I wanted. Even better than when I was on JBoss 2.2.2.
I did try changing the conversion pattern to [%c] from [%c{1}]. However this did not change anything in the logging. I did it both on the default and console appender. Are you sure that shows the full category name?
Chris Heady -
3. Re: Verbose JBoss Logging
neut6o1 Jan 4, 2002 4:39 PM (in response to neut6o1)One more thing, I see the entire category name in log4j logs that I have created, but not in ones like "[Container Factory]" and "[Default]". I guess those must be from a different log4j.properties file.
Chris Heady -
4. Re: Verbose JBoss Logging
adrian.brock Jan 4, 2002 5:01 PM (in response to neut6o1)Hi.
JBoss used to use its own custom logger.
It has gradually moved to log4j exclusively.
As of 3.0 the old logger is gone.
[Default] is System.out.println which log4j
intercepts. :-)
Regards,
Adrian -
5. Re: Verbose JBoss Logging
neut6o1 Jan 4, 2002 5:54 PM (in response to neut6o1)Thanks again warjort. The information you have given me has really helped.