You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Marc Boorshtein <mb...@gmail.com> on 2024/05/29 23:10:16 UTC

Forward messages for specific queues only

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

Re: Forward messages for specific queues only

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Maybe you can use static defined destinations instead of dynamic ?

Regards
JB

On Thu, May 30, 2024 at 3:14 PM Marc Boorshtein <mb...@gmail.com> wrote:
>
> >
> >
> > You can exclude the destinations which are problematic, mixing
> > dynamic/exclude/static on the transport connector:
> >
> >
> OK, so i can explicitly exclude destinations, but i can't limit which
> destinations get included exclusively?  OK, I can manage that.  I can
> exclude the DLQ at least so that way it doesn't get processed by remote
> brokers.
>
> Thanks
> Marc
>
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@activemq.apache.org
For additional commands, e-mail: users-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact

Re: Forward messages for specific queues only

Posted by Marc Boorshtein <mb...@gmail.com>.
>
>
> You can exclude the destinations which are problematic, mixing
> dynamic/exclude/static on the transport connector:
>
>
OK, so i can explicitly exclude destinations, but i can't limit which
destinations get included exclusively?  OK, I can manage that.  I can
exclude the DLQ at least so that way it doesn't get processed by remote
brokers.

Thanks
Marc

>
>

Re: Forward messages for specific queues only

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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 <mb...@gmail.com> 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: users-unsubscribe@activemq.apache.org
For additional commands, e-mail: users-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact