[
https://issues.apache.org/jira/browse/AMQ-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316472#comment-15316472
]
ASF subversion and git services commented on AMQ-6310:
------------------------------------------------------
Commit 2b03e6a9422dc40729bd8cc5a4c235a1631a5d83 in activemq's branch
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=2b03e6a ]
https://issues.apache.org/jira/browse/AMQ-6310
Merging fix for AMQ-6310
This closes #188
> Certain VirtualTopic configurations no longer send messages to the correct
> queue
> --------------------------------------------------------------------------------
>
> Key: AMQ-6310
> URL: https://issues.apache.org/jira/browse/AMQ-6310
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.13.0
> Reporter: Jonathan Malek
> Assignee: Christopher L. Shannon
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
