[ https://issues.apache.org/jira/browse/AMQ-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291591#comment-16291591 ]
ASF subversion and git services commented on AMQ-6875: ------------------------------------------------------ Commit 94aea677acab41fc8ba425c9fefc9c351fb31a94 in activemq's branch refs/heads/activemq-5.15.x from [~cshannon] [ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=94aea67 ] AMQ-6875 - Use the correct destination for Virtual destination consumers when using Virtual Topics (cherry picked from commit 56baba96c657d4e44b88955a964d6c92ff39b822) > Virtual destination consumers can create invalid demand for Virtual Topics > -------------------------------------------------------------------------- > > Key: AMQ-6875 > URL: https://issues.apache.org/jira/browse/AMQ-6875 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, networkbridge > Affects Versions: 5.15.2 > Reporter: Christopher L. Shannon > Assignee: Christopher L. Shannon > Fix For: 5.16.0, 5.15.3 > > > When testing out Virtual topics over a network bridge that has the virtual > destination consumers feature enabled I noticed that the consumer advisories > were wrong. The destinations sent as part of the consumer advisories to > create demand over the bridge are using the name of the Virtual Topic. > This is causing extra demand to flow across the network bridge in some cases > because by default the VirtualTopic name is "VirtualTopic.>" . So once one > Virtual Topic is created on a remote broker then any messages sent to > "VirtualTopic.>" on the local broker will be forwarded over to the other > broker even if there is no VirtualTopic matching. > The solution is to make sure to use the actual topic that the VirtualTopic is > subscribed to as part of the advisory messags. -- This message was sent by Atlassian JIRA (v6.4.14#64029)