had a quick look at the code, you use consumer.dispatchAsync=false which ensures that a single thread does the dispatch, which will not allow for any of the network latency to accumulate. Leave this at the default true so that dispatch happens using two threads. Also, set decreaseNetworkConsumerPriority=true on the network connector. nc.setDecreaseNetworkConsumerPriority(true);
On 12 October 2010 18:14, jpeng <jp...@xmatters.com> wrote: > > I have changed my test case and set the prefetch for the fast consumer to 100 > and the prefetch for the slow consumer is still 1. The results didn't really > change. 50 messages were processed by the fast consumer and 50 messages were > processed by the slow consumer. > Attached is the test case and the logs from the test: > http://activemq.2283324.n4.nabble.com/file/n2992321/SharedQueueTest.java > SharedQueueTest.java > http://activemq.2283324.n4.nabble.com/file/n2992321/amq.logs amq.logs > > > Thanks, > Jim > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Configuring-Distributed-Queues-in-Store-Forward-Network-tp2967501p2992321.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://blog.garytully.com Open Source Integration http://fusesource.com
