Standardise queue Ownership accross protocols
---------------------------------------------
Key: QPID-2576
URL: https://issues.apache.org/jira/browse/QPID-2576
Project: Qpid
Issue Type: Bug
Reporter: Martin Ritchie
Currently the broker does not have a consistent view of who the queue Owner is.
The 0-8/0-9/0-91 code path uses client id.
The 0-10 code path uses the authenticated user name.
In a number of locations such as:
DerbyMessageStore uses the authenticated Principal name.
QueueDeclareHandler compares principal name against getOwner for exclusive
queue checks.
(This will only work if a 0-10 client created the queue as it will set the
owner name to the principal name, see sub jira on this issue)
>From the JMS Spec 4.3.2
The purpose of the client identifier is to associate a connection and its
objects
with a state maintained on behalf of the client by a provider. By definition,
the
client state identified by a client identifier can be `in use' by only one
client at
a time. A JMS provider must prevent concurrently executing clients from using
it.
Which suggests that it could be used to perform exclusive queue detection
rather than the authenticated user that could log in more than once. This will
need more discussion on dev.
First step is to ensure the code all uses getOwner even if the 0-10 version
currently sets that to the authenticated Principal.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
