Successful message to AMQ Broker queue also appears in DLQ
Issue
When a message is delivered successfully to the target queue via an exclusive divert the
<address-setting match="#">
<dead-letter-address>DLQ</dead-letter-address>
<expiry-address>ExpiryQueue</expiry-address>
<redelivery-delay>0</redelivery-delay>
<!-- with -1 only the global-max-size is in use for limiting -->
<max-size-bytes>-1</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>PAGE</address-full-policy>
<auto-create-queues>true</auto-create-queues>
<auto-create-addresses>true</auto-create-addresses>
<auto-create-jms-queues>true</auto-create-jms-queues>
<auto-create-jms-topics>true</auto-create-jms-topics>
<send-to-dla-on-no-route>true</send-to-dla-on-no-route>
</address-setting>
<diverts>
<divert name="SourceToTarget">
<address>SourceAddress</address>
<forwarding-address>TargetAddress</forwarding-address>
<exclusive>true</exclusive>
</divert>
</diverts>
Environment
Red Hat AMQ
7.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.