The DLQ support for MDB really is handled by the EJB container, and is not part of JBoss Messaging itself. There are several pluggable DLQ strategies, see:
http://docs.jboss.org/jbossas/javadoc/4.0.3SP1/connector/org/jboss/resource/adapter/jms/inflow/dlq/package-summary.html It does seem that there is no way to look at the exception/cause of redelivery. For MDB, you're actually not supposed to throw exceptions from onMessage(). So, by design you would never know the "cause." If you want to get fancy, track your failures some other way... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068965#4068965 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068965 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
