peek at http://activemq.apache.org/maven/apidocs/org/apache/activemq/plugin/SubQueueSelectorCacheBroker.html
the idea is that a plugin will retain the info about consumers selectors so even if they disconnect for a while, the virtual topic will retain or dispatch messages for it. This allows you to keep the selectorAware option. On 12 February 2015 at 20:26, Llama007 <[email protected]> wrote: > Hello > We have a situation we are using a Virtual Destination with a message > selector. The virtual destination is NOT selectorAware because we want to > get messages when there are no consumers on the queue. This has the effect > of forwarding every message sent to the Virtual Topic to the destination > queue regardless of if it matches the message selector or not. This means > messages that will never be subscribed by the message selector will > eventually fill up the queue. > Is there any way to clean up those 'unselected' messages short of creating > another consumer with a message selector that negates the original message > selector? > > We are using ActiveMQ 5.10 > > Thanks > Tim > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Virtual-Destination-selector-with-unwanted-messages-tp4691474.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
