Several of our brokers have a VirtualTopic with the name VirtualTopic.> and a prefix of *.*.. The expected behavior would be that a message sent to VirtualTopic.A should be consumed on a queue with any pattern that matches *.*.VirtualTopic.A.
For example, if a message is published to a topic called VirtualTopic.A, that would be consumed on queues Consumer.A.VirtualTopic.A and Subscriber.A.VirtualTopic.A.
However, since the change made in
AMQ-6058, it appears that, given the example above, neither queue receives the message. This is because the change performs a startsWith comparison of the destination against the prefix, rather than a regex comparison.
If there is a reason to prevent leading wildcards in the prefix, it should be documented, otherwise the sanity check in shouldDispatch(...) needs to be updated to handle it.