Keith Wall created QPID-8164:
--------------------------------
Summary: [Broker-J] [AMQP 1.0] [BINDMAP] temporary-queue do not
enforce connection exclusivity
Key: QPID-8164
URL: https://issues.apache.org/jira/browse/QPID-8164
Project: Qpid
Issue Type: Bug
Components: Broker-J
Reporter: Keith Wall
The JMS 2.0 specification, 6.2.2 Creating temporary destinations, says:
{quote}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.
{quote}
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)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
