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.
