Hi Marc,
You can exclude the destinations which are problematic, mixing
dynamic/exclude/static on the transport connector:
<dynamicallyIncludedDestinations>
<queue physicalName="include.test.foo"/>
<topic physicalName="include.test.bar"/>
</dynamicallyIncludedDestinations>
<excludedDestinations>
<queue physicalName="exclude.test.foo"/>
<topic physicalName="exclude.test.bar"/>
</excludedDestinations>
<staticallyIncludedDestinations>
<queue physicalName="always.include.queue"/>
<topic physicalName="always.include.topic"/>
</staticallyIncludedDestinations>
Regarding the DLQ, it's not possible to change the DLQ name with the
shared dead letter strategy. However, you can use an individual dead
letter strategy instead.
Regards
JB
On Thu, May 30, 2024 at 1:10 AM Marc Boorshtein <[email protected]> wrote:
>
> I've got two AMQ classic instances connected via <networkConnectors>:
>
> AMQ1:
>
> <networkConnector uri="static:(ssl://amq.apps.192-168-2-14.nip.io:61616)"
> >
> <dynamicallyIncludedDestinations>
> <queue physicalName="openunison.k8s.obj.dr1" />
> </dynamicallyIncludedDestinations>
> </networkConnector>
>
> AMQ2:
> <networkConnector uri="static:(ssl://
> amq.apps.192-168-2-89.nip.io:61616)" >
> <dynamicallyIncludedDestinations>
> <queue physicalName="openunison.k8s.obj.dr" />
>
> </dynamicallyIncludedDestinations>
> </networkConnector>
>
> Messages pushed to openunison.k8s.obj.dr get forwarded as expected and are
> processed by the remote queue and the client of the remote queue. The
> problem is that the queue instances use overlapping names, so a message
> sent to AMQ1 --> AMQ2 and is processed by a consumer on AMQ2. Is there a
> way to limit forwarding to specific queue names only? If not, is there a
> way to rename the ActiceMQ.DLQ?
>
> Thanks
> Marc
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
