Hi Nicolas- The selector is cached from first consumer registration until it is replaced by a new consumer registration. The selector is also written to disk so it will become active on broker restart, so there is no loss between broker startup and consume connecting.
The selector will be active the entire time it is registered with the broker up until a new selector is provided by a new consumer— in your example, that would be step #3 when the second selector would become active and the first selector is deactivated. Thanks, Matt Pavlovich > On Oct 21, 2024, at 4:58 AM, CASAUX Nicolas <nicolas.cas...@soprasteria.com> > wrote: > > > Hello ! > > I have a question regarding the VirtualSelectorCacheBrokerPlugin mentioned > here : > https://activemq.apache.org/components/classic/documentation/virtual-destinations > > If a consumer follows those actions in order: > > 1. subscribes to a queue "Consumer.consumer01.VirtualTopic.invoices" with > selector "k1=v1" > 2. disconnects > 3. reconnects and subscribes to the same queue > "Consumer.consumer01.VirtualTopic.invoices" with a new selector "k2=v2" > > How long will the "k1=v1" condition will be used to forward message from the > topic to the queue ? Will it be forever ? > I could not find such info in the docs, and I was not able to find it in the > code. (I saw the 10 mn scheduler to persist selectors, but it's another topic) > > Thanks in advance! > > Regards, > Nicolas > > > C2 - Usage restreint --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org For additional commands, e-mail: users-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
