Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2071

consumer.exclusive is not respected for AMQP clients

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • JBoss A-MQ 6.3.x
    • JBoss A-MQ 6.3
    • broker
    • None
    • Hide

      I have tested this with the the simple C example that comes with the QPid Proton distribution. It is in directory examples/c/reactor. I run it like this, in two different client sessions:

      ./receiver -a amqp://localhost:5672 -s fred?consumer.exclusive=true -i c2 -c 0

      The -i (client ID) value must be different in each session. "-c 0" means to consume messages indefinitely. If I post messages to the queue "fred" then I see then going alternately to the different clients, rather than only to one.

      Show
      I have tested this with the the simple C example that comes with the QPid Proton distribution. It is in directory examples/c/reactor. I run it like this, in two different client sessions: ./receiver -a amqp: //localhost:5672 -s fred?consumer.exclusive= true -i c2 -c 0 The -i (client ID) value must be different in each session. "-c 0" means to consume messages indefinitely. If I post messages to the queue "fred" then I see then going alternately to the different clients, rather than only to one.

      Consumer clients that use JMS/OpenWire can specify the attribute "consumer.exclusive=true" on the destination name, to create an exclusive consumer. The same approach does not work with AMQP clients, even though the attribute is passed over the wire, and the broker does parse the name from the name+attribute string correctly. The broker does not raise any error, it just ignores the attribute.

            gtully@redhat.com Gary Tully
            rhn-support-kboone Kevin Boone
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: