Return-Path: 
 <users-return-20263-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: (qmail 35062 invoked from network); 31 Aug 2009 23:08:42 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 31 Aug 2009 23:08:42 -0000
Received: (qmail 33863 invoked by uid 500); 31 Aug 2009 23:08:36 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 33786 invoked by uid 500); 31 Aug 2009 23:08:36 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 33587 invoked by uid 99); 31 Aug 2009 23:08:36 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Aug 2009 23:08:36 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Aug 2009 23:08:27 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1MiFyo-00054p-T0
	for users@activemq.apache.org; Mon, 31 Aug 2009 16:08:06 -0700
Message-ID: <25231814.post@talk.nabble.com>
Date: Mon, 31 Aug 2009 16:08:06 -0700 (PDT)
From: "praveen.sharma" <praveen.sharma@ll.mit.edu>
To: users@activemq.apache.org
Subject: ApacheMQ 5.3, Topic priority
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: praveen.sharma@ll.mit.edu
X-Virus-Checked: Checked by ClamAV on apache.org


How is priority handled for ActiveMQ Topics?  Are the messages for the higher
priority topics guaranteed to be dispatched before then the ones with the
lower priority messages?

For example, will configuring jms uri in ApacheCamel (1.6.1) (as described
at http://camel.apache.org/jms.html and shown below) ensure that topic foo
will have a higher priority and topic bar will have a lower priority?
<from
uri="jms:topic:foo&amp;maxMessagesPerTask=-1&amp;priority=9&explicitQoSEnabled=true"/>
<from
uri="jms:topic:bar&amp;maxMessagesPerTask=-1&amp;priority=4&explicitQoSEnabled=true"/>


-- 
View this message in context: http://www.nabble.com/ApacheMQ-5.3%2C-Topic-priority-tp25231814p25231814.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.