A-MQ 6 on OpenShift - Many "Duplicate message add attempt rejected" messages and DLQ build-up
Issue
With three or more brokers in a fully-connected mesh, and consumers using durable subscriptions, various failure scenarios can lead to a situation where duplicate messages are passed between brokers. Although the broker detects these messages, the default action is to send them to the dead letter queue (DLQ), which can cause problems with storage, particularly if they are not consumed from this destination.
Environment
- Red Hat A-MQ
- 6.3 (and probably other versions)
- Red Hat OpenShift
- 3.11 (and probably other versions)
- Brokers are in fully-connected mesh
- Consumers use durable subscriptions
Although the problem is particularly noticeable on OpenShift, other installations using a fully-connected mesh may well have similar problems.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
