Elliot, This looks very similar to an issue fixed a couple of months ago. Check out: http://fusesource.com/issues/browse/MB-438 or alternatively for AMQ: https://issues.apache.org/activemq/browse/AMQ-2104
HTH, -Giovani On Wed, Apr 29, 2009 at 1:21 PM, Elliot Barlas <elliotbar...@gmail.com>wrote: > > I have been experimenting with the behavior of a network of two AMQ brokers > and message selecting consumers. As described in the AMQ documentation > (http://activemq.apache.org/networks-of-brokers.html), consuming with > message selectors in a broker network environment can lead to messages > being > trapped on one of the brokers. > > Setup: > -2 AMQ Brokers connected by static URIs. Using all default settings. > -2 Producers, 1 connected to each Broker. > -Each producer sends 100 non persistent, non expiring messages. > -1 message selecting consumer connects to 1 Broker and consumes all > matching > messages. > -Observation: the 100 messages from the other Broker (without the consumer) > are transferred over, EVEN THOSE MESSAGES THAT DO NOT MATCH THE SELECTOR > EXPRESSION. THOSE MESSAGES ARE NOW TRAPPED ON THAT BROKER. > > How can I avoid transferring messages for which there is no consumer than > can ACTUALLY consume the messages??? > > I have condensed the experiment into a small Java class and attached it: > http://www.nabble.com/file/p23296281/SelectorBrokerNetworkTest.java > SelectorBrokerNetworkTest.java > > Thanks, > Elliot > -- > View this message in context: > http://www.nabble.com/Issues-with-Network-of-Brokers-and-Message-Selectors-tp23296281p23296281.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
