The named queue concept can be realized in configuration using filtered destination that use selectors. see; http://activemq.apache.org/virtual-destinations.html#VirtualDestinations-Usingfiltereddestinations
As the selectors are evaluated at send time there is no limit imposed by sparse matching. On 9 September 2010 21:19, Fredrik Jonson <fred...@jonson.org> wrote: > Gary Tully wrote: > >> yea, this is a known issue with sparse selectors. increasing the >> maxPageSize via a destination policy entry for that queue will help as >> it will ensure that more messages are held in memory for dispatch. > > Well, yes it helps, but only as long as the message your selector wants > can be found within the configured page size. > >> see: the comments on >> http://trenaman.blogspot.com/2009/01/message-selectors-and-activemq.html > > The last sentence on the above post offer a very good alternative. If you need > to adress messages by type and must be able to handle a backlog bigger than > what is possible to contain in the maxPageSize, replace your selectors with > separate named queues, each specific for whatever you selected for before. > > This assumes that you do not have too many selectors though, and obviously > that your selector queries can be mapped to named queues. > > -- > Fredrik Jonson > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
