5.11.0 Trying to validate if our current setup is configured properly for virtual topics with message selectors in a broker network. Based on preliminary observations, virtual topics appear to works as expected; producers send on topics, consumers receive on queues, regardless of where they reside in the network. We did, however, observe the following problem:
Virtual topic producer sends 10 messages, consumer gets 7 messages, then we kill the consumer to force a reconnect. When consumer connects back, the remaining 3 messages are not forwarded to the consumer, they appear stuck on the queue. If the producer sends new messages, the consumer, oddly, receives the new messages. I found this post, it suggests disabling conduit subs on queue connectors, but enabling it on topic connectors (currently we disable it for both) http://activemq.2283324.n4.nabble.com/conduit-subscriptions-td2365115.html#a2365117 ## Virtual topic interceptor ## We deviated from standard virtual topic conventions due to our security model, but it works <virtualDestinationInterceptor> <virtualDestinations> <virtualTopic name="*.*.*.vtopic.*" prefix="" postfix=".*" selectorAware="true" /> ## network connector <networkConnector name="queue-connector1" networkTTL="12" conduitSubscriptions="false" suppressDuplicateQueueSubscriptions="true"> <dynamicallyIncludedDestinations> <queue physicalName=">"/> </dynamicallyIncludedDestinations> </networkConnector> <networkConnector name="topic-connector-1" networkTTL="12" conduitSubscriptions="false"> <dynamicallyIncludedDestinations> <topic physicalName=">"/> </dynamicallyIncludedDestinations> </networkConnector> -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
