It is not too importnat; by default, a dispatch to a consumer occurs on its connection thread so it does not block dispatch to other consumers or a message send, so it would be possible to use this technique to selectively block consumers. With asyncDispatch=false, it would not be possible to be selective.
On 11 July 2012 11:36, mandjeo <[email protected]> wrote: > I didn't get what you meant by asyncDispatch. > > I tried with blocking preProcessDispatch and it works. > > Thanks a lot !!! > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Pausing-messages-consuming-tp4653866p4653880.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://fusesource.com http://blog.garytully.com
