Switching default log4j threshold
Mike McCune
mmccune at redhat.com
Thu Jan 21 06:00:52 UTC 2010
I spent 30 minutes being frustrated that I couldn't see any changes
affected by adding DEBUG packages to our log4j config file. No mater
what I did, my console wouldn't show the additional output.
I realized it was the Threshold setting in our config file.
Anyone object if I bump this to DEBUG? Why would we permanently want to
hide DEBUG from the console output. Seems pointless
diff --git
a/modules/enterprise/server/container/src/main/resources/jbossas/server/default/conf/jboss-log4j.xml
b/modules/enterprise/se
index 8ec0af5..4702cdd 100644
---
a/modules/enterprise/server/container/src/main/resources/jbossas/server/default/conf/jboss-log4j.xml
+++
b/modules/enterprise/server/container/src/main/resources/jbossas/server/default/conf/jboss-log4j.xml
@@ -23,7 +23,7 @@
<param name="Target" value="System.out"/>
<!-- Appender will not log any messages with priority lower than
INFO even if the category's priority is set lower.
So essentially, this means DEBUG and TRACE messages will
never be output to the console -->
- <param name="Threshold" value="INFO"/>
+ <param name="Threshold" value="DEBUG"/>
--
Mike McCune
mmccune AT redhat.com
Red Hat Engineering | Portland, OR
Systems Management | 650.254.4248
More information about the rhq-devel
mailing list