You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Stephen Baker (Jira)" <ji...@apache.org> on 2021/04/20 21:40:00 UTC

[jira] [Created] (ARTEMIS-3259) broker-connection mirror does not strip anycastPrefix

Stephen Baker created ARTEMIS-3259:
--------------------------------------

             Summary: broker-connection mirror does not strip anycastPrefix
                 Key: ARTEMIS-3259
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3259
             Project: ActiveMQ Artemis
          Issue Type: Bug
    Affects Versions: 2.17.0
         Environment: artemis 2.17.0

I have seen this both in docker on macOS, and running on a linux server (without docker).
            Reporter: Stephen Baker


Setup two instances that use broker-connection mirroring to replicate from one to the other.

On both instances add the anycastPrefix as documented in the acceptors note e.g.:

{{<acceptor name="artemis">tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpDuplicateDetection=true;anycastPrefix=jms.queue.;multicastPrefix=jms.topic.</acceptor>}}

 and add a broker-connection on the primary instance e.g.:

<broker-connections>
 {{  <amqp-connection uri="(tcp://artemis-1-m:5672,tcp://artemis-1-mb:5672)" name="DRMirror1M" user="artemis" password="artemis" auto-start="true">}}

{{     <mirror message-acknowledgements="true"/>}}
 {{  </amqp-connection>}}
 </broker-connections>

 

Then send a couple messages to a queue on the primary instance, some using the prefixed address some without.

Observe that all of the messages are on the queue on the primary instance, but on the mirror only the messages without the prefix are on the queue. If you setup a second queue on the mirror with an address that includes the prefix those messages get delivered to it instead.

No messages appear in the log to indicate a problem.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)