[ARTEMIS-4416] Client can't use anycast without FQQN

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Information Provided
• Affects Version/s: 2.7.0, 2.28.0
• Assignee: Justin Bertram
• Reporter: Damien Picard
• Created: 01/Sep/23 16:30
• Updated: 07/Sep/23 20:33
• Resolved: 07/Sep/23 20:02

Description

Since artemis-jms-client@2.7.0, it's no longer possible to create an ActiveMQQueue object with an address (only FQQN). 

Use case:
1. We have an address with one or more queues (declare with an anycast router).
2. We create filters to distribute our messages to the correct queue
3. A producer sends a message to an address and the server is responsible for forwarding it to the correct queue.

This use case works in 2.6.4. Since 2.7.0, we have an error raised by the "checkDestination" method ("Destination xxx does not exist, address exists but autoCreateQueues=false").

ActiveMQ Artemis lets you do this, but the client prevents it.

If we're using ActiveMQTopic, it works exclusively in multicast mode, so the above use case doesn't work either.

Also, we could use FQQN exclusively, but we didn't design our architecture that way.