[jboss-dev-forums] [JBoss ESB Development] - Re: Performance Improvement Prop: Cache PortReference.extend

[dward]

"Kevin.Conner at jboss.com" wrote : So DEBUG is still enabled, and being invoked, but not being logged?  Eeek.

Out-of-the-box, the (.org ESB) default profile's jboss-log4j.xml is configured such that the FILE appender will output DEBUG statements to server.log.  This can be changed if you add a non-DEBUG Threshold to the FILE appender (it currently doesn't have a Threshold set)
<param name="Threshold" value="INFO"/>
, or you can just remove the FILE appender completely.

The CONSOLE appender is set with a Threshold of INFO, so you don't see any DEBUG output, however debug statements are still called (logger.isDebugEnabled() still returns true) unless you uncomment this section:
<!-- Limit JBoss categories
  | <category name="org.jboss">
  |    <priority value="INFO"/>
  | </category>
  | -->
to set the log level of that logger.  So, in summary, log events are still being created (which means unecessary debug code like String-building is still occurring), even if the Threshold of the Appender is filtering them out.  We need to stop the events from being fired in the first place, which means setting a priority/level on the right logger categories.

Can I change this along with JBESB-3044, or should it be it's own Jira issue?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269638#4269638

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269638