Do I understand correctly - messages go into the DLQ when "container managed transaction handling is used" and do not do so when the same is not used?
If so, what is managing the transactions? Is it possible that the transactions just never rollback after the MDB throws an exception? In other words - could the transactions be lingering, or actually committing? Bottom line here - there needs to be a rollback on the transaction, when XA or JMS transactions are active, in order for the message to get routed to the DLQ. I believe there is some logging (either debug level or trace level) that will show enough detail on the client to track this down further. -- View this message in context: http://activemq.2283324.n4.nabble.com/Message-not-redirected-to-DLQ-when-exception-thrown-by-MDB-tp4709187p4709239.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
