Uploaded image for project: 'Qpid'
  1. Qpid
  2. QPID-8164

[Broker-J] [AMQP 1.0] [BINDMAP] Dynamic nodes created with the temporary-queue capability do not enforce connection exclusivity

    XMLWordPrintableJSON

    Details

      Description

      The JMS 2.0 specification, 6.2.2 Creating temporary destinations, says:

      Temporary destinations (TemporaryQueue or TemporaryTopic objects) are destinations that are system-generated uniquely for their connection. Only their own connection is allowed to create consumer objects for them.

      Currently when the Qpid JMS Client is used with Broker-J, the last sentence whilst being enforced by the client is not enforced by the Broker.  This means that if the temporary destination were to be passed to another party - say as a JMSReplyTo, that client would be able to create a consumer, violating the JMS specification.

      I think Broker-J ought to be detecting the terminus capability temporary-queue specified by amqp-bindmap-jms-v1.0-wd09 and then applying the correct queue exclusivity policy.

       I think the same problem may apply to the temporary-topics too (but not confirmed)

       

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              kwall Keith Wall
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: