Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of christian.posta@gmail.com
 designates 209.85.217.181 as permitted sender)
MIME-Version: 1.0
Date: Fri, 29 Mar 2013 07:32:25 -0700
Message-ID: 
 <CAKS7T5PKCDM-iDsQQBr=z+3_iJENwY5m11FCgpA09dwcfsdSig@mail.gmail.com>
Subject: JMS client automatically reorders prefetched messages by default
From: Christian Posta <christian.posta@gmail.com>
To: "users@activemq.apache.org" <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary=089e011607cad8701f04d9112311

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

Seems like it might be an unintended ordering consequence? or is it covered
by the JMS spec? I suspect the latter, but wanted to discuss anyway...
Per this JIRA, https://issues.apache.org/jira/browse/AMQ-2790 client-side
priority support was created, but also made default. So in this case, a
producer sending messages with priority values set on the messages would be
reordered in the consumer according to priority regardless of whether
priority is enabled on the broker side.

However, the JMS spec says this about priority:

"JMS does not require that a provider strictly implement priority ordering
of messages; however, it should do its best to deliver expedited messages
ahead of normal messages."

-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

--089e011607cad8701f04d9112311--