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: jms.prefetchPolicy.queuePrefetch=1 means 2 outstanding messages?
Date Thu, 15 Nov 2012 15:47:24 GMT
try with PolicyEntry usePrefetchExtension=false, the use case for that
came originally from the RAR, but I think it will work.

btw: what issues do you have with the pull model, prefetch=0

On 15 November 2012 15:26, himanshu_s83 <himanshu_s83@yahoo.co.in> wrote:
> Hi!
>
> We have a case whereby we've set jms.prefetchPolicy.queuePrefetch=1 and we
> see that we have 2 outstanding messages in consumer's session queue. 1
> getting processed and 1 waiting. Problem is that the processing message
> might take long time to complete and send ack back to Broker causing the
> other message to keep waiting forever, waiting for the existing processing
> message to get completed.
>
> Can we change this waiting message number to 0 so that session queue doesn't
> have any unconsumed message so that Broker can dispatch that waiting message
> to some other free consumer. Right now we have free consumers but due to
> this long processing time of currently getting processed message, the other
> message keeps waiting forever.
>
> If I put it to 0, it becomes pull model which also we have some problems. We
> want push model only but only 1 message per consumer which is under
> processing i.e no other message should wait for this consumer if other
> consumers are free.
>
> Thanks
> Himanshu
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/jms-prefetchPolicy-queuePrefetch-1-means-2-outstanding-messages-tp4659398.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.



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

Mime
View raw message