...
If a message is being redelivered, it means that a previous attempt to deliver the message failed due to some reason. If a message is being redelivered multiple times, it can be because the message is bad in some way. When such a message is being redelivered over and over again, it wastes resources and prevents subsequent good messages from being processed.
When you work with the ESB Profile of WSO2 Enterprise Integrator (WSO2 EI) allows , you to can detect such repeatedly redelivered messages using the JMSXDeliveryCount property that is set in messages.
Detecting Being able to detect repeatedly redelivered messages is particularly useful since it makes it possible because you can take necessary steps to handle such messages in a proper manner. For example, consume you can consume such a message and send the messages it to a separate queue.
The following diagram illustrates how the ESB Profile of WSO2 EI can be used to detect repeatedly redelivered messages, and store such messages in an internal message store.
...
To demonstrate the scenario illustrated above, we will let's configure the JMS inbound endpoint in the ESB Profile of WSO2 EI using HornetQ as the message broker. This sample scenario includes the following sections:
...
This configuration creates an inbound endpoint to the JMS broker and has a simple sequence that logs the message status using the JMSXDeliveryCount value.
To build the sample
- Start the ESB Profile of WSO2 EI with the sample configuration.
...
When you analyze the output on the WSO2 EI ESB console, you will see an entry similar to the following:
...