Re: Re:Clarifcation on KahaDB support for message priority is needed

The clientside message priority is kinda the "default" approach to handling priority.. no config is needed (on the broker, or the client side) to enable it... if a producer is sending messages with JMSPriority, then when the consumer sees it in its prefetch, it will do its best to order them approp

Re: Re:Clarifcation on KahaDB support for message priority is needed

Excellent article! You really took time detailing priority support issues on ActiveMQ broker's side. I wish you could get into a bit more specifics on “Client side message priority” – googling jms.messagePrioritySupported didn’t bring much… How does it impact final message consumption priority-wise

Re: Re:Clarifcation on KahaDB support for message priority is needed

I've added some clarifications to the wiki ( http://activemq.apache.org/how-can-i-support-priority-queues.html), including an indepth treatment at my blog: ActiveMQ Message Priorities: How it works http://www.christianposta.com/blog/?p=289 let me know if you have feedback. Cheers On Fri, Mar 22,

Re: Re:Clarifcation on KahaDB support for message priority is needed

Ok. Thanks. -- View this message in context: http://activemq.2283324.n4.nabble.com/Clarifcation-on-KahaDB-support-for-message-priority-is-needed-tp4665014p4665057.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Re:Clarifcation on KahaDB support for message priority is needed

You cannot assume 100% correct 0-9 priority order all the time. The broker will strive to deliver fully in order priority as best it can (in the index, in the store cursors/subscription cursors, and on the client), however that behavior can change slightly based on your config and messaging proper

Re: Re:Clarifcation on KahaDB support for message priority is needed

It's been a bit confusing... According to http://activemq.apache.org/message-cursors.html : The store based cursor also handles cursors for non-persistent messages, which are not stored in the message store. Non-persistent messages are passed dire

Re:Clarifcation on KahaDB support for message priority is needed

Since the broker has the pending message cursor as well so your messages are reordered by the cursor of the broker at first.Your client may reorder the messages again if prefetch is enabled. The two pending message cursors are fully priority-support so you won't see the fifo order no matter if yo