This forum is for user problems related to
JMS (Java Message Service) and
MDB (Message Driven Beans)
It is also the support forum for JBossMQ
Tips on asking questions the correct way to get an answer http://jboss.org/wiki/Wiki.jsp?page=JBossHelp
More information can be found on the wiki page http://jboss.org/wiki/Wiki.jsp?page=JBossMQ
Alternate configurations can be found in docs/examples/jms,
please contribute back if you have new ones.
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"/>
</category>
e.g. for mdbs
<category name="org.jboss.jms">
<priority value="TRACE" class="org.jboss.logging.XLevel"/>
</category>
<category name="org.jboss.ejb.plugins.jms">
<priority value="TRACE" class="org.jboss.logging.XLevel"/>
</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
But don't dump your whole log/server.log here. Nobody will read it. If you suspect a deadlock or hang post a thread dump:
On unix ctrl-\ or kill -3 <jboss-pid>
On windows ctrl-break
Regards,
Adrian
