You may need to disable concurrentStoreAndDispatch on the kahaDB persistence adapter so that the messages pass through the cursors.
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/store/kahadb/KahaDBMessagePriorityTest.java?view=markup On 25 August 2010 14:23, Kondro <wayne.robin...@gmail.com> wrote: > > I have the following section in my config file: > > <policyEntry queue=">" producerFlowControl="true" memoryLimit="5mb" > prioritizedMessages="true"/> > > and I am using 4 for my default and 9 for my high priority messages which > show up in the queue browser when I look at the messages. > > When I connect to the queue, I use the following string: > QUEUENAME?consumer.prefetchSize=1 > > However, my messages are still being consumed in the order they are added, > not based on their priority. > > What am I missing? > > > Gary Tully wrote: >> >> javax.jms.Message#DEFAULT_PRIORITY = 4 >> >> normal priority == javax.jms.Message#DEFAULT_PRIORITY >> >> low priority < javax.jms.Message#DEFAULT_PRIORITY >> >> >> > > -- > View this message in context: > http://old.nabble.com/Method-setMessagePrioritySupported%28true%29-called-on-ActiveMQConnectionFactory-doesn%27t-work-tp29490144p29532203.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com