Thank you for the information. I will definitely try using the latest version. --- Regards Iliya Grushevskiy
> 25 сент. 2025 г., в 18:05, Robbie Gemmell <[email protected]> > написал(а): > > Following up on my earlier reply > (https://lists.apache.org/thread/jxfm258rlmwrnl9h68svppt7x11g8zvc) on > your original thread to dev@, this is the related fix I was > remembering: > > https://issues.apache.org/jira/browse/ARTEMIS-4799 > > On Thu, 25 Sept 2025 at 15:43, Iliya Grushevskiy <[email protected]> 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. >> — >> Regards >> Iliya Grushevskiy >> >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > For further information, visit: https://activemq.apache.org/contact > >
