Hello Tim, thanks for your answer! Well, the other possibility is the acknowledge mode /Dups-ok-acknowledge/. I tried this without success. I also tried to rollback the user transaction in the MDB instead of throwing an exception with both acknowledge modes. I don't get any redeliveries, nor are the messages redirected to the DLQ.
The JMS specification says the following: /AUTO_ACKNOWLEDGE With this acknowledgment mode, the session automatically acknowledges a client's receipt of a message either when the session has successfully returned from a call to receive or when the message listener the session has called to process the message successfully returns./ This may be interpreted as if the container may acknowledge the message, when it has received the message from the broker but before /onMessage()/ of the MDB has been called. In this case I understand the behaviour. But then there is no difference to the acknowledge mode /Dups-ok-acknowledge/. The only mode, which may be helpful is /CLIENT_ACKNOWLEDGE/, but this is not valid for MDB's. Regards Thomas -- View this message in context: http://activemq.2283324.n4.nabble.com/Message-not-redirected-to-DLQ-when-exception-thrown-by-MDB-tp4709187p4709204.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
