On 9/25/25 10:43, Iliya Grushevskiy wrote:
Hi, I am creating a receiver for the broker connection between Artemis and ActiveMQ (Classic) using AMQP. The correct link is created, specifying the queue that matches the filter, so the source and target are set to the queue name. ActiveMQ Classic correctly determines which queue to read from and sends the corresponding messages. However, it sets the value of the message's address field with the queue:// prefix. When Artemis receives a message with this address, it forwards it to an address that includes the prefix, which is strange and unexpected. It seems that the address field in the ProtonServerReceiverContext should also be populated when creating a receiver in a broker connection. This would ensure that the message is sent to the correct destination.Example of amqp connection: <amqp-connection auto-start="true" name="WITH-CLASSIC" reconnect-attempts="-1" retry-interval="5000" uri="tcp://localhost:61617"> <receiver address-match="TEST"/> </amqp-connection> Resulting in messages been sent to queue://TEST The description refers to version 2.30, but based on the code, it seems that the address determination logic has not changed in version 2.42. While it is true that support for bridges and federation has been added, these features work with messages in an on-demand mode, which is different from the receive logic.
While AMQP federation is solely demand based, the AMQP bridge feature is not, you can configure it to not consider demand and simply pull messages based on configuration. The AMQP bridge feature that was added include a much wider set of configuration options meant to aid in use cases where the two servers are not both Artemis brokers so I would strongly encourage an upgrade and test using that mechanism over trying to use the likely soon to be deprecated receivers mechanism
— Regards Iliya Grushevskiy
-- Tim Bish --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
