...
Configuring standard JMS message acknowledgment patterns
The following are JMS acknowledgment patterns introduced by JMScan be used:
- Auto Acknowledge
- Duplicates Allowed
- Client Acknowledge Transacted Acknowledgement
- Acknowledge: The messages transmitted through the session are automatically acknowledged by the message receiving client.
- Duplicates Allowed: When this acknowledgment method is used, the messages will be acknowledged automatically but not always. This means that duplicate messages can sometimes go through a session. However, each message will be acknowledged at least once.
- Client Acknowledge: The method of message acknowledgment should be enabled at the client end and not by the broker (JMS provider) sending the message.
- Transacted Acknowledgement: With this method, the client creates a transacted session with the broker (JMS provider) and messages are acknowledged automatically. Once all messages in the transaction are acknowledged, the messages will be committed to the subscriber client.
| Excerpt | ||||
|---|---|---|---|---|
| ||||
Only for MB 3.2.0. Therefore, this section will be valid for EI 6.1.0. Configuring per-message acknowledgmentWith 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.
or,
|
