qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Mallassi <olivier.malla...@gmail.com>
Subject Re: [C++ Broker][JMSSelector][AMQP 1.0] problem with JMSCorrelationID while using JMS Selector
Date Tue, 22 Dec 2015 17:37:15 GMT
not sure I got your question but I would answer : competing consumers

In fact, in AMQP 1.0,
- if I connect my consumer on a destination which is a topic, with
JMSSelector, this works but I get a subscription that I cannot share
between multiple consumers (so no load balancing). maybe it can work if I
do not use JMS but proton-j or an API that gives me access to the link
- if I connect to a queue, my JMSSelector is applied on the queue (which
fills up with the messages that do not match the selector)

on the other hand, if I do this in AMQP 0.10, this is almost straigh
forward: publish to headers exchange, bind your queues (config), then you
have competing consumers on each queues.

So, as I would like to continue using JMS as the API, I guess I was trying
to rely more on the broker capabilities to filter / route my messages. not
sure this is the good approach, btw.

On Tue, Dec 22, 2015 at 5:57 PM, Gordon Sim <gsim@redhat.com> wrote:

> On 12/22/2015 04:09 PM, Olivier Mallassi wrote:
>> (my apologies for bothering you with all these questions...)
> Not at all!
> It looks like JMSType (subject) or JMSCorrelationID are not used (or that
>> my binding is false).
> The subject should match if you use that as the binding key when creating
> the binding (instead of ''). The headers exchange won't look at the
> correlation-id though I'm afraid.
> Is there a particular reason you need/want a headers exchange as opposed
> to just using a selector on a topic subscription (to e.g. a fanout
> exchange)?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message