In 5.0, consumer priorities, as described in this page, does not work as advertised.
http://activemq.apache.org/consumer-priority.html See this thread http://www.nabble.com/Consumer-Priority-on-AMQ-5.0-to14369093s2354.html#a14369093 One possible alternative is to assign different prefetch limits to your consumers so that the broker will stream more messages to those consumers having higher limits. http://activemq.apache.org/what-is-the-prefetch-limit-for.html Joe James.Strachan wrote: > > On 09/01/2008, qwidjibo <[EMAIL PROTECTED]> wrote: >> >> >> Hi All. >> >> I'd like to have many (potentially hundreds or more) message listeners in >> the same VM listening to different queues. >> >> The problem is that I'd like a number of those to be listening at >> different >> priorities. Looking at the JMS spec as well as the amq implementation, it >> looks like the consumer priority is established for the connection as a >> whole, not the individual session or subscription. >> >> Are there any ways around this? I can imagine engineering solutions (e.g. >> maintaining a set of connections , one for each priority level in use), >> but >> that seems likely to introduce a fair deal of unwanted complexity. My >> main >> concern here is bloating the number of threads in the AMQ instance >> itself...at it does have a habit of creating a few for each connection. > > You can configure consumer priority on a per consumer basis using > destination URIs > http://activemq.apache.org/consumer-priority.html > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com > > -- View this message in context: http://www.nabble.com/Using-different-consumer-priorities-in-the-same-connection-tp14722765s2354p14735854.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
