(my apologies for bothering you with all these questions...)
let's say I am sending messages using the JMS / AMQP 1.0 client with JMS
properties set, e.g:
Message message = session.createTextMessage(".....");
message.setJMSType("mysubject"); //mapped to the amqp subject
https://issues.apache.org/jira/browse/QPID-6432
...
message.setJMSCorrelationID("abc");
message.setStringProperty("color", "blue");
message.setIntProperty("weight", 2600);
producer.send(message);
into a destination which is, in that case, *a header exchange* (but AMQP
1.0 does care about that).
on the broker side (cpp version), is there a way to subscribe to this
header exchange and use the JMS headers? (this is less rich than
JMSSelector but good enough)
./qpid-tools-0.32/build/scripts-2.7/qpid-config -b 192.168.56.102:12000 add
exchange headers subjects
./qpid-tools-0.32/build/scripts-2.7/qpid-config -b 192.168.56.102:10000 add
queue mysubscription
./qpid-tools-0.32/build/scripts-2.7/qpid-config -b 192.168.56.102:10000
bind subjects mysubscription '' any color='blue', amqp.correlation_id='abc'
It looks like JMSType (subject) or JMSCorrelationID are not used (or that
my binding is false).
Cheers.
On Tue, Dec 22, 2015 at 11:11 AM, Robbie Gemmell <robbie.gemm...@gmail.com>
wrote:
> On 22 December 2015 at 09:39, Gordon Sim <g...@redhat.com> wrote:
> > On 12/22/2015 09:22 AM, Olivier Mallassi wrote:
> >>
> >> by the way, wen I consume from a node that is a topic, the JMS / AMQP
> 1.0
> >> creates a queue with an uniqueID for each receiver (e.g.
> >>
> >>
> MyComponent_qpid-jms:receiver:ID::3008640b-8ac6-4c87-9485-6156773c79b7:1:1:1:payments)
> >
> >
> > Actually that queue is created on the broker side. The name comes from
> the
> > container id and link name.
> >
> >> - is there a way to auto-delete this "queue" when the consumer JVM shut
> >> down?
> >
> >
> > It should be auto-deleted by default, unless the client requests
> otherwise.
> > Is it a durable subscription on the topic that you created?
> >
> >> - is there a way to share this "queue" between multiple consumers so
> that
> >> they can compete each other?
> >
> >
> > At the AMQP protocol level, all receiving links that request a 'shared'
> > capability on the link and use the same link name (from the same topic
> > obviously) will share the subscription (i.e. the messages from that
> > subscription will be distributed between them). (This is not a standard
> > capability).
> >
> > I'm not sure if the JMS client will allow you to set the capabilities
> though
> > (Robbie?).
>
> Not at present no. Having some defined method/syntax for configuring
> lower level AMQP link/terminus details to other values within the JMS
> client is something thats been mentioned in passing in the AMQP
> BINDMAP TC, but we have yet to look into it further.
>
> > At some point the JMS client will support JMS 2.0 which includes
> > the notion of shared subscriptions and as part of that a standard
> approach
> > at the protocol level will hopefully emerge.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>
