5.1 logging issue

[brettallen]

i'm trying to increasing the logging level of both Hibernate and JBossWS.

i changed ..../server/default/conf/jboss-log4j.xml by:

• adding a category for org.hibernate and
• uncommented the org.jboss.ws.core.MessageTrace category

   <category name="org.hibernate">
      <priority value="TRACE"/>
   </category>
 
   <!-- Enable JBossWS message tracing  -->
   <category name="org.jboss.ws.core.MessageTrace">
     <priority value="TRACE"/>
   </category>
 
 

I do not see jboss reload the jboss-log4j.xml file when it changes, and i don't see any change in the logging output, even after restarting jboss.

I've seen similiar questions asked on this topic, but didn't see an answer.

is it just me, or is there something that i am missing?

thanks in advance.

[peterj]

Do you see this line in the FILE appender in the jboss-log4j.xml file:

<param name="Threshold" value="${jboss.server.log.threshold}"/>

By default, jboss.server.log.threshold is set to INFO. You need to either pass a new setting on the command line, or change/delete/comment-out this line in the file.

[rohit.macherla]

Hi Peter,

Doesn't adding a <category> element override the "Threshold" value of the FILE appender and provide us with more control on the log file ? I am a bit confused here, because I remember reading that the <category> elements exist to give us a better control over what part of the application requires deep/shallow logs.

Cheers,

Rohit M

[peterj]

No. Both <category> and Threshold are filters, but at different levels. A <category> indicates whether the logging system should even be concerned with the log message. If the logging system decides that is should be concerned with the log messages, it then polls each appender to see which ones will accept it based on their Threshold settings.