Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates
 209.85.210.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1360765228697-4663327.post@n4.nabble.com>
References: <1351602826261-4658449.post@n4.nabble.com>
	<1360765228697-4663327.post@n4.nabble.com>
Date: Mon, 25 Feb 2013 12:21:33 +0000
Message-ID: 
 <CAH+vQmMWK8cgrfp8aFGDrWh=RCNgq1a3HDQndS8F9giwyhkJkA@mail.gmail.com>
Subject: Re: Reorder of messages
From: Gary Tully <gary.tully@gmail.com>
To: "users@activemq.apache.org" <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary=bcaec5396512ddb78a04d68b9411

--bcaec5396512ddb78a04d68b9411
Content-Type: text/plain; charset=ISO-8859-1

On 13 February 2013 14:20, dannygallagher2@gmail.com <
dannygallagher2@gmail.com> wrote:

> ..
> One question about priority messages:
> When a message is consumed by priority, isn't that really the same as using
> a selector?
> ActiveMQ must be looking at everything in the queue, just like a selector
> would. Correct?
>

The difference between priority and selectors is that the index is
in priority order, there is a view of all messages from the index.
In kahaDb we effectively keep 3 indices. (low, med, hi)
selectos need to be run on the entire message so the message needs to be in
memory, hence the pageSize and limitations.

For the jdbc store, the DB does the work on the messages table (we index
with priority and message id), thus the full 0-9 range of priority is
easily supported.


-- 
http://redhat.com
http://blog.garytully.com

--bcaec5396512ddb78a04d68b9411--