a slow consumer will keep at maximum "prefetch" number messages from other consumers. The dispatch loop will ignore any "full" consumers. I think setting prefetch to 0 will alleviate the symptom you are seeing. http://activemq.apache.org/what-is-the-prefetch-limit-for.html
On 27 May 2011 09:38, Nakul Chakrapani <nakulchakrapani....@gmail.com> wrote: > Hi all , > > Can anyone tell me how to change the mesage dispatch policy in apache > activeMQ ( am using version 5.4.2). > As all of u know , default dispatch policy is RoundRobin. But the > problem with that policy is , if one consumer goes down or is blocked for > some reason , other consumers ll not receive the messages even if there are > some messages in the queue. > I want to change the dispatch policy , such that even if one of the > consumers go down , other consumers must continue their work without > depending upon other clients. > I also used setDispatchAsync() method , but it didnt help. > Please help me in this regard. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-message-Dispatch-policies-tp3554700p3554700.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://fusesource.com http://blog.garytully.com
