Hi there,
Pretty much what the title says -- we have a configuration with the
following in the broker XML that appears to override the default virtual
destination naming conventions and, effectively, disables virtual
destinations:
<destinationInterceptors>
<virtualDestinationInterceptor>
<virtualDestinations>
</virtualDestinations>
</virtualDestinationInterceptor>
</destinationInterceptors>
...Does this sound correct and is it expected?
Thanks for your time.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Does-empty-virtualDestinations-in-broker-XML-disable-virtual-destinations-tp4704179.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.