Return-Path: X-Original-To: apmail-qpid-users-archive@www.apache.org Delivered-To: apmail-qpid-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 CD364981E for ; Wed, 5 Oct 2011 14:41:19 +0000 (UTC) Received: (qmail 82604 invoked by uid 500); 5 Oct 2011 14:41:19 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 82535 invoked by uid 500); 5 Oct 2011 14:41:19 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 82527 invoked by uid 99); 5 Oct 2011 14:41:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Oct 2011 14:41:19 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pmoravec@redhat.com designates 209.132.183.24 as permitted sender) Received: from [209.132.183.24] (HELO mx3-phx2.redhat.com) (209.132.183.24) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Oct 2011 14:41:13 +0000 Received: from mail02.corp.redhat.com (zmail02.collab.prod.int.phx2.redhat.com [10.5.5.42]) by mx3-phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p95EeqVv000952 for ; Wed, 5 Oct 2011 10:40:52 -0400 Date: Wed, 05 Oct 2011 10:40:52 -0400 (EDT) From: Pavel Moravec To: users@qpid.apache.org Subject: Re: Priority queues with JMS Client/ Java Broker Message-ID: <16219a11-1cb3-44a2-ac24-05fd3831bc7c@zmail02.collab.prod.int.phx2.redhat.com> In-Reply-To: <4E8C5D12.6050605@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Originating-IP: [10.34.1.224] X-Mailer: Zimbra 7.1.2_GA_3268 (ZimbraWebClient - FF3.0 (Linux)/7.1.2_GA_3268) > From: "Alan Conway" > To: users@qpid.apache.org > Cc: "Pavel Moravec" > Sent: Wednesday, October 5, 2011 3:35:14 PM > Subject: Re: Priority queues with JMS Client/ Java Broker > > On 09/27/2011 03:37 AM, Pavel Moravec wrote: > > Hi Praveen and all, > > just an additional info to prevent some confusion if you wish to > > use browse mode: priorities work when consuming the messages, > > while when browsing the queue, messages are ordered based on their > > enqueueing time. I.e. when sending messages: > > > > - first with priority 2 > > - then with priority 1 > > - latest with priority 3 > > > > then browsing the queue shows messages in ordering "priority 2", > > "priority 1", "priority 3" message. > > While consuming messages consumes them in ordering "priority 3", > > "priority 2", "priority 1" message. > > > > That sounds like a bug to me. Is it intentional? I think so - I discussed it with somebody (Gordon?). At present it is intentional as the change would not be trivial afaik. Kind regards, Pavel --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org