Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5D5F618CC5 for ; Wed, 6 May 2015 12:12:56 +0000 (UTC) Received: (qmail 12398 invoked by uid 500); 6 May 2015 12:12:56 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 12369 invoked by uid 500); 6 May 2015 12:12:56 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 12356 invoked by uid 99); 6 May 2015 12:12:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 May 2015 12:12:55 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.164.171.186 which is an MX secondary for users@activemq.apache.org) Received: from [54.164.171.186] (HELO mx1-us-east.apache.org) (54.164.171.186) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 May 2015 12:12:51 +0000 Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 9F39C42E76 for ; Wed, 6 May 2015 12:12:30 +0000 (UTC) Received: by layy10 with SMTP id y10so5767084lay.0 for ; Wed, 06 May 2015 05:10:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=1Zi9jL20089QP4tMV+9I8nzBjl2LAPY/Hx+gDtxRFfU=; b=CEZeXcemTtcXXfd15mUhWnAugkTBTOUu1oiU5yZxH1XO54ISL+D5PCUzydHAyKpTYL X6wN8bFBx1sRYRHYvpsnh/iYUs/s5GsuhbFee0pm8IPwTtsjpF/IaVmakMBsYtyN6BBh MNOBg6g8R9VOOkjv5XAHrHBMg1LrVntXVPC+xm/3szuVmUeOblgajX3XAmCOBtsdN2XZ Aq19ojRNGbGe+lne/UU8j1IOx1ILR7P2K1vIVYV2hWMORl1V6TB/+a3cAn0hq/wWEuFX eQaCnjdrGrTosB5Ru5Tvgl/Ivmo6TL6EPAjHwRLbxGHt3bFLvav6bnJVlsy82c7M3OF6 DlIw== MIME-Version: 1.0 X-Received: by 10.152.27.194 with SMTP id v2mr2286573lag.75.1430914259268; Wed, 06 May 2015 05:10:59 -0700 (PDT) Received: by 10.152.162.13 with HTTP; Wed, 6 May 2015 05:10:59 -0700 (PDT) In-Reply-To: References: Date: Wed, 6 May 2015 13:10:59 +0100 Message-ID: Subject: =?UTF-8?Q?Re=3A_Does_JMS_priority_work_with_=E2=80=9Csmall=22_maxPageSiz?= =?UTF-8?Q?e_=3F?= From: Gary Tully To: "users@activemq.apache.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org that is true, the dispatch goes through the cursors in batches once memory (or the cursor cache) is exhausted. For durable subs, there is the ability to bypass the paged in messages, see= : https://github.com/apache/activemq/blob/165959e25007271f8cdfdcf72641b9a9248= 3ef40/activemq-unit-tests/src/test/java/org/apache/activemq/store/MessagePr= iorityTest.java#L83 I know folks have asked for something similar for queue cursors. It would make a nice enhancement but may be tricky to get right. On 4 May 2015 at 19:14, Kevin Burton wrote: > Let=E2=80=99s say you have a queue with 1M items.. they are all low prior= ity. Then > you add a high priority entry. > > I believe, due to message cursors, that it won=E2=80=99t be executed unti= l it=E2=80=99s > read into the =E2=80=9CmaxPageSize window=E2=80=9D. > > Is this correct or does it depend on the underlying store? > > KahaDB and LevelDB could probably move it to the head (I think) but the > memory store can not... > > -- > > Founder/CEO Spinn3r.com > Location: *San Francisco, CA* > blog: http://burtonator.wordpress.com > =E2=80=A6 or check out my Google+ profile >