Re: Virtual topics, custom prefix limitations

We may need to support standard subscribers to the virtual topic, but it's not a drop-dead requirement. Having said that, we verified the broker network is working for standard queues/topics using the above configuration, but not virtual topics, even after removing . VT's are only working when

Re: Virtual topics, custom prefix limitations

BTW, do you have consumers consuming directly from the virtual topic, or only via queues? If you have no topic consumers, I believe you can just remove your excludedDestinations entry and everything will work as intended. As I understand it, the problems only occur when you have a mix of queue

Re: Virtual topics, custom prefix limitations

Correct, statically include the topics, not the queues. On Oct 15, 2016 9:27 AM, "Devlin" wrote: > Ok, just to be clear, we define the virtual topic statically (the one used > by > the producer), not the individual consumer queues. I hope it's the former > because

Re: Virtual topics, custom prefix limitations

Ok, just to be clear, we define the virtual topic statically (the one used by the producer), not the individual consumer queues. I hope it's the former because client queues for virtual topics are named using "app-version" convention for grouping related consumers; we can't define those names

Re: Virtual topics, custom prefix limitations

I believe that listing all virtual topics in the staticallyIncludedDestinations element would work. Please let us know if it works, so that the next person knows whether this is an option for them. Tim On Oct 14, 2016 9:07 PM, "Devlin" wrote: > Tim, > > The