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 appropriately.
This won't get you too far if priority is not enabled in the broker and your consumer prefetch gets filled. It does "somewhat" fulfill the JMS spec of "do its best to deliver expedited messages ahead of normal messages" On Tue, Apr 2, 2013 at 9:31 AM, mikmela <[email protected]> wrote: > 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? > > Overall conclusion, it’s hard at this time to get it working on ActiveMQ > without really understanding of broker/consumer infrastructure internals… > May be ActivemMQ version 6 should address it via true Message > Priority-supported Queue where all these flags, caching mechanisms and etc > are opaque to user and enablement of it straight forward and relatively > simple. It could be a good selling point when choosing JMS provider... > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Clarifcation-on-KahaDB-support-for-message-priority-is-needed-tp4665014p4665379.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
