A subscriber client receiving messages from a queue or topic in the broker should be configured to send an acknowledgment back to the broker when the messages are received. There are several acknowledgment methods that can be used by the subscriber.
Configuring the time taken to acknowledge messages
There are several acknowledgment models defined in JMS specification 1.1. To configure the time within which consumers can acknowledge messages, you can set the AndesAckWaitTimeOut entry in the JMS client as follows:
System.setProperty("AndesAckWaitTimeOut", "30000");
If the acknowledgment fails within the above time, the client informs the broker that the message is rejected. The message is then scheduled to be redelivered later by the server.
Configuring standard JMS message acknowledgment patterns
The following are acknowledgment patterns introduced by JMS:
- Auto Acknowledge
- Duplicates Allowed
- Client Acknowledge
- Transacted Acknowledgement
Configuring per-message acknowledgment
With Per Message Acknowledge we can acknowledge each message as per requirement. Any message that is not acknowledged will go through the same process as when client acknowledged such as the message getting rejected.
Following is a sequence diagram on how an example scenario will work:
Use the enum org.wso2.andes.jms.Session.PER_MESSAGE_ACKNOWLEDGE available in the andes-client jar or the value 259 when creating the session.
import org.wso2.andes.jms.Session; QueueSession queueSession = queueConnection.createQueueSession(false, Session.PER_MESSAGE_ACKNOWLEDGE);
or,
QueueSession queueSession = queueConnection.createQueueSession(false, 259);