One add on: I think, rolling back the user transaction cannot work here, because the user transaction has not been started by the container. So the container doesn't recognize this rollback. So the only way to tell the container, that the message cannot be processed is by throwing an exception.
-- View this message in context: http://activemq.2283324.n4.nabble.com/Message-not-redirected-to-DLQ-when-exception-thrown-by-MDB-tp4709187p4709252.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
