My expectation is that a remote client must process all messages. I understand the nodes that a local (e.g. MDB) will see only the local queue, but this might be ok because other nodes will have its own MDB-Queue combination.
But you make me thoughtfully and getting doubts about
Thanks Wolf-Dieter. But as Yanyan points out, we only have one consumer (across both local queues in the cluster), not one consumer per queue, which seems to be the scenario for which jboss messaging was designed, based on the JBMCluster wiki page above.
I suppose the question really is: was jboss messaging ever designed to work correctly with one consumer and multiple clustered queues? (ie. where the consumer is able to receive all messages, from both queues, with only a single JMS connection)
It would be helpful to know for certain whether we are attempting to chase after a goal that is unattainable, rather than it just being a matter of not figuring out the correct configuration yet. Yanyan and I have spent about 6 full days or so trying to get this working, trying many many different configurations and reading just about every piece of related documentation available on the web.
Can anyone answer this question (about the intended design/purpose of JBM) with finality?
I am encountering the same issue here: a single consumer to multiple clustered queues. Have you figured out the issue yet?