Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (athena.apache.org: domain of gsim@redhat.com designates
 209.132.183.28 as permitted sender)
Message-ID: <54CF76DD.4020708@redhat.com>
Date: Mon, 02 Feb 2015 13:08:45 +0000
From: Gordon Sim <gsim@redhat.com>
Organization: Red Hat UK Ltd, Registered in England and Wales under Company
 Registration No. 3798903, Directors: Michael Cunningham (USA), Matt Parsons
 (USA), Charlie Peters (USA), Michael O'Neill (Ireland)
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: users@qpid.apache.org
Subject: Re: usage of message selectors in C++ Qpid 0.28 client (amqp 1.0)
References: <1422462276266-7619011.post@n2.nabble.com>
 <CAOhBXQ796GeMPQh_7LOne9sYJCQZQnsOgzUBVW7YwxyuDVrFTA@mail.gmail.com>
 <CAOhBXQ7jLbqpMVgi9mCRhTELx+hmv68-kAwO_nWyFw68zRmkhw@mail.gmail.com>
In-Reply-To: 
 <CAOhBXQ7jLbqpMVgi9mCRhTELx+hmv68-kAwO_nWyFw68zRmkhw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 01/30/2015 03:15 PM, Jakub Scholz wrote:
> So, I did some playing around. And it looks like the filter configured this
> way works fine with Qpid C++ broker, but doesn't really work with ActiveMQ.
> The filter seems to be present in the attach commands, but seems to be
> ignored by the broker.
>
> 2015-01-30 16:00:50 [Protocol] trace
> [19d9dcef-2e7c-4738-b549-e8a3c5737c22]: 0 -> @attach(18)
> [name="queue://responseQueue_0dd729c8-6782-4380-affb-05ce401a75d3",
> handle=0, role=true, snd-settle-mode=2, rcv-settle-mode=0,
> source=@source(40) [address="queue://responseQueue", durable=0, timeout=0,
> dynamic=false, filter={:selector=@77567109365764 "status='licha'"}],
> target=@target(41) [address="queue://responseQueue", durable=0, timeout=0,
> dynamic=false], initial-delivery-count=0]
> 2015-01-30 16:00:50 [Protocol] trace
> [19d9dcef-2e7c-4738-b549-e8a3c5737c22]: 0 <- @attach(18)
> [name="queue://responseQueue_0dd729c8-6782-4380-affb-05ce401a75d3",
> handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0,
> source=@source(40) [address="queue://responseQueue", durable=0,
> expiry-policy=:"session-end", timeout=0, dynamic=false,
> filter={:selector=@77567109365764 "status='licha'"}], target=@target(41)
> [address="queue://responseQueue"], incomplete-unsettled=false,
> initial-delivery-count=0]
>
> Anyone has an idea why it doesn't work? The Java client seems to work fine
> with the selector and ActiveMQ.

ActiveMQ looks only at the name of the filter, not the descriptor of the 
value, and expects it to be 'jms-selector'.

You can control that by being more explicit in the address, e.g.:

   my-queue; {link:{filter:{name:jms-selector, 
descriptor:'apache.org:selector-filter:string', value:'uniqueAppId=7'}}}

ActiveMQ should really look at the descriptor, but we could also change 
the name/key the client uses by default since a compliant broker doesn't 
really care what that is anyway.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org