A single node "holds" the messages and the other nodes consume them. If a single consumer is sufficiently fast, then the other nodes end up idle.
You may want a more round-robin configuration for your queue: | <mbean code='org.jboss.mq.server.jmx.Queue' name='jboss.mq.destination:service=Queue,name=SMX'> | <attribute name="ReceiversImpl">org.jboss.mq.server.ReceiversImplLinkedList</attribute> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3888706#3888706 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3888706 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
