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.