Queue with ‘Maximum Redelivery Count’ set (Redeliver Forever disabled), and a DMQ configured.If you want messages that reach the maximum redelivery count to go to a DMQ, you need: Published messages can have a ‘Message-TTL’ and must be ‘DMQ-Eligible’. Queue with ‘Respect-TTL’ enabled, a DMQ configured, and optionally a ‘Maximum-TTL’ specified. If you want messages that expire to go to a DMQ, you need: That is an important point that bears repeating: Messages must be DMQ-Eligible! Without this set, the messages will be deleted from the original queue when they lose delivery eligibility. Note that messages will not be moved into a DMQ unless they are published with the flag ‘DMQ-Eligible’. Once created, the DMQ is configured on the original endpoint in the ‘DMQ Name’ field. How do I use a Dead Message Queue with Solace PubSub+ Event Broker?Ī DMQ on Solace PubSub+ Event Broker is configured as a normal queue and can be created in the same manner on the Queue page of PubSub+ Broker Manager. Once exceeded, the message will be removed from the endpoint or can be moved to a DMQ. To ensure an application does not get stuck in this loop, an endpoint can be set to redeliver a message a maximum number of times with the setting ‘Maximum Redelivery Count’. In this case, the message is referred to as a poison message. When that application reconnects to the endpoint, it will receive the same message and would be stuck in a loop. This scenario could occur when a consumer is unable to process a message and crashes before sending an application acknowledgement.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |