On Thu, 2010-12-23 at 09:22 -0800, rliguori wrote: > "I think this part of the spec is terrible." > >> It does leave a lot to be desired. > > "It is so vague you can do nothing to order by priority and still claim > compliance. " > >>I agree it is vague, but my interpretation is that "something" must be > implemented. Examine this statement, "it should do its best to deliver > expedited messages ahead of normal messages". I would hope that the JMS > implementers would interpret this as some type of algorithm must be in place > to expedite messages with higher priority, and if there isn't one then the > implementation is not meeting compliancy. That is, if nothing is done, then > the implementation is NOT doing its best to deliver expedited messages ahead > of normal messages, as no attempt was made.
Message Priority Support was added in ActiveMQ 5.4.2. If your messages are all arriving with priority 4 then your producer is sending them with that priority as that's the default JMS defined value. Did you set the priority on the MessageProducer ? Regards -- Tim Bish ------------ FuseSource Email: tim.b...@fusesource.com Web: http://fusesource.com Twitter: tabish121 Blog: http://timbish.blogspot.com/
