OK, since this works in one container (WebLogic) and not another (WildFly) - my suspicion is with the container handling of the exception.
Turning up the logging on org.apache.activemq.ActiveMQSession to DEBUG on the JMS client should cause the following to get logged: * ... Transaction Commit :... * ... Transaction Rollback, txid: ... TRACE level logging may provide even more insight. DEBUG logging on org.apache.activemq.broker.TransactionBroker on the broker itself may also provide more insight. Hope this helps. -- View this message in context: http://activemq.2283324.n4.nabble.com/Message-not-redirected-to-DLQ-when-exception-thrown-by-MDB-tp4709187p4709308.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
