Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <23322595.post@talk.nabble.com>
Date: Thu, 30 Apr 2009 13:02:33 -0700 (PDT)
From: Elliot Barlas <elliotbarlas@gmail.com>
To: users@activemq.apache.org
Subject: Re: Issues with Network of Brokers and Message Selectors
In-Reply-To: <23322585.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <23296281.post@talk.nabble.com>
 <467bc4630904292026x1c6e9b05r214b97e295f20014@mail.gmail.com>
 <36e91d9d0904300005l5adde5afja9a324d4fd507a64@mail.gmail.com>
 <23322585.post@talk.nabble.com>


I should add that I am using AMQ core version 5.2.0, so I am not benefiting
from recent bug fixes regarding this issue such as the one mentioned above.


Elliot Barlas wrote:
> 
> I have tried that as you can see from the attached code.  It still does
> not work.  
> 
> 
> Dejan Bosanac wrote:
>> 
>> Hi Elliot,
>> 
>> you have to turn off conduit subscriptions in order to have selectors
>> work
>> over the network. Take a look at this link for more details
>> 
>> http://activemq.apache.org/networks-of-brokers.html#NetworksofBrokers-WhentouseandnotuseConduitsubscriptions
>> 
>> Cheers
>> --
>> Dejan Bosanac
>> 
>> Open Source Integration - http://fusesource.com/
>> ActiveMQ in Action - http://www.manning.com/snyder/
>> Blog - http://www.nighttale.net
>> 
>> 
>> On Thu, Apr 30, 2009 at 5:26 AM, Giovani Seben <gseben@gmail.com> wrote:
>> 
>>> 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 <elliotbarlas@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.
>>> >
>>> >
>>>
>> 
>> 
>> -----
>> Dejan Bosanac
>> 
>> Open Source Integration - http://fusesource.com/
>> ActiveMQ in Action - http://www.manning.com/snyder/
>> Blog - http://www.nighttale.net
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Issues-with-Network-of-Brokers-and-Message-Selectors-tp23296281p23322595.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.