activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: Queue/Message Fairness as oppose to Client Fairness
Date Wed, 08 Aug 2012 13:48:07 GMT
What you want goes against the grain a bit, the broker wants to
dispatch messages as fast as it can for each destination.

Using lazyDispatch=true will reduce the queue dispatch loop to what
can be immediately sent, so when that is combined with a low prefetch,
eg prefetch=1, the minimum number of messages per destination will be
processed at a time.


On 8 August 2012 11:32, tapan.thapa <tapan.thapa2000@gmail.com> wrote:
> Hello,
>
> Thanks for the suggestion however i tried with php stomp 1.0 as well as with
> Java client and both are not working as expected.
>
> PHP Client:
> PHP consumer get all messages from first queue than second queue and so on.
>
> Java Client:
> Java client is good as it receives 3-4 messages per queue in round robin.
> sometime 4-5-10 (Can not predict) messages.
>
> However i am expecting 1 message from each queue in round robin (Does not
> matter if consumer is in java or in php).
>
> Settings now are:
>
> <policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb"
> maxPageSize="1">
>                 </policyEntry>
>               <taskRunnerFactory>
>       <taskRunnerFactory maxIterationsPerRun="1"/>
>     </taskRunnerFactory>
>
> Kindly suggest.
>
> Regards
> Tapan Thapa
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Queue-Message-Fairness-as-oppose-to-Client-Fairness-tp3423122p4654892.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.



-- 
http://fusesource.com
http://blog.garytully.com

Mime
View raw message