JBossMQ Logging

To configure JBossMQ logging for debugging, enable TRACE logging to look for funny behaviour, this is configured in conf/log4j.xml, e.g. for jbossmq

   <category name="org.jboss.mq">
     <priority value="TRACE" class="org.jboss.logging.XLevel"></priority>
   </category>

e.g. for mdbs

   <category name="org.jboss.jms">
     <priority value="TRACE" class="org.jboss.logging.XLevel"></priority>
   </category>
   <category name="org.jboss.ejb.plugins.jms">
     <priority value="TRACE" class="org.jboss.logging.XLevel"></priority>
   </category>

If you are having problems on the client side, add the following

log4j.properties to your classpath

log4j.rootCategory=INFO, Default

# Dumps logging into jbossmq.log
log4j.appender.Default=org.apache.log4j.FileAppender
log4j.appender.Default.File=jbossmq.log
log4j.appender.Default.layout=org.apache.log4j.PatternLayout
log4j.appender.Default.layout.ConversionPattern=%d %-5p [%c(1)] {%t} %m%n
log4j.appender.Default.Append=false

# TRACE level logging
log4j.category.org.jboss.mq=TRACE#org.jboss.logging.XLevel

# Uncomment to filter invocation layer (transport) logging
#log4j.category.org.jboss.mq.il=INFO

Referenced by: