DMQ Eligible Flag set on Publisher (violates pub sub principles)
The principles for pub sub are to decouple publishers and subscribers from each other.
That publisher need to set DMQ Eligible to true (default = false) impacting a correct set-up on subscriber to make use of DMQ (Dead Message Queue) is violating this principle.
Even worse as subscriber has done everything correct:
- Created DMQ
- Linked DMQ to main queue
- Defined TTL
- Defined limited retry (not unlimited)
but if publisher does not set that flag the messages would get lost. (discarded)
That is even risky as message loss is worst to happen on message flows.
- So can anyone explain the rational and purpose of that flag ?
- Why can it not be turned as default to: true (instead of false) or even removed ?
- Why does it get switched back from true to false when storing message in DMQ ?
(that make easy copy of messages from DMQ back to main queue more complex then needed). As when moving back message from DMQ to main queue you must set it back to true as on re-publish again an error could occur which should park message again back to DMQ. Not set would loose message.