To get more control of the scheduling, you will need to specify the TaskRunnerFactory for the broker and specify 1 for the maxIterationsPerRun so that it will move on to another task (each destination dispatch is a task) immediately.
It may be helpful if you can provide a junit test case for your use case such that we can be on exactly the same page w.r.t to the requirement here. There may be more than one way to solve this. On 4 April 2011 19:11, kapitalx <a...@pagerduty.com> wrote: > Garry, Thanks for the suggestion. With the change, the broker continues to > dispatch everything from Queue 1 before moving onto Queue 2. Just much > slower. I still need the dispatching to alternate between queues for every > message. > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Queue-Message-Fairness-as-oppose-to-Client-Fairness-tp3423122p3426201.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://blog.garytully.com http://fusesource.com
