After some more digging it seem to be the failover transport that might be
the culprit. When posting a msg directly to one node
tcp://server_1:61616
the filter is applied correctly. But using the failover transport when
posting the msg
failover:(tcp://server_1:61616,tcp://server_2:61616)
Hi!
I've got a VirtualTopic with configuration selectorAware=true. I've realized
that you're basically forced to use the virtualSelectorCacheBrokerPlugin to
avoid getting offline consumers missing messages. I'm using a network of
brokers setup, with two nodes. The plugin only has support for file