How to acknowledge messages in Message Driven Beans

Question

In the JMS documentation I read that Message Driven Beans doesn't support CLIENT_ACKNOWLEDGE mode, only DUPS_OK_ACKNOWLEDGE and AUTO_ACKNOWLEDGE.

As I understand it, in AUTO_ACKNOWLEDGE mode, the message is acknowledged (deleted from the destination) when the onMessage method is invoked. What I want is to tell my broker not to delete messages from the destination (queue or topic) when something bad happens

There must be some way to do this. Anyway, why is CLIENT_ACKNOWLEDGE not supported in Message Drven Beans.

AUTO_ACKNOWLEDGE deletes the message *after* onMessage is successfully called — Konstantin, Sep 23 '15 at 06:46

raffian · Accepted Answer · 2014-02-12T14:21:36.307

7

What I want is to tell my broker not to delete messages from the destination (queue or topic) when something bad happens.

If you're configured to use PERSISTENT messages, any exceptions in onMessage() will persist the message for redelivery based on broker and destination settings. If you're using NON_PERSISTENT messages, any exception in onMessage() typically discards the message.

Anyway, why is CLIENT_ACKNOWLEDGE not supported in Message Driven Beans.

Message-driven beans are managed by the J2EE container; as such, the container handles acknowledgements. Typically, only stand-alone JMS receivers should use CLIENT_ACKNOWLEDGE.

What messaging middleware are you using?

edited Feb 12 '14 at 14:21

answered May 21 '13 at 15:41

raffian

31,267
26
103
174

This is exactly the information I found out today researching. :) But thanks anyway! I use OpenMQ on Glassfish server. – Amer A. May 22 '13 at 08:29
"any exceptions in onMessage() will persist the message for redelivery " -- should I throw the exception in onMessage? But I cannot because onMessage method is implemented and it doesn't throw the exception. – Noor Syed Aug 26 '14 at 19:34
@NoorSyed That's a problem because once `onMessage()` completes successfully, it's consumed. – raffian Aug 27 '14 at 01:07
1

Persistence settings are for handling failures ( infra structure or JMS/Application server crashes). They are NOT about redelivery after an exception is thrown from application code – Konstantin Sep 23 '15 at 06:45

score 0 · Answer 2 · answered Sep 23 '15 at 06:41

Just make sure you are using (JTA) transactions (the default is that you are using them). Then make sure your applications server has a redelivery setting and or a Dead Letter Queue (DLQ). Any exceptions thrown from your MDB will then trigger a redelivery and after a certain amount of failures the message will be moved to the DLQ.

The redeilvery setting is called "max-delivery-attempts" in Wildfly for instance

score 0 · Answer 3 · answered Jul 30 '18 at 10:11

In Mdb you can tell the broker to not delete the message trough 'MessageDrivenContext'. (Without throwing exception - which also rollbacks the transaction)

Some example code, Where you can handle all exceptions in method 'onMessaage' and set a rollback in case of Exception:

@MessageDriven(name = "queueMDB", activationConfig = {
    @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
    @ActivationConfigProperty(propertyName = "destination", propertyValue = "TestQueue"),
    @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
}
public class TestMdb implements MessageListener {

    @Resource
    private MessageDrivenContext messageDrivenContext;

    @Override
    public void onMessage(Message message) {
        try {
            // Some usefull code...
        }
        catch (Exception e) {
            messageDrivenContext.setRollbackOnly();
        }
    }
}

How to acknowledge messages in Message Driven Beans

3 Answers3