[
https://issues.apache.org/jira/browse/QPID-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206998#comment-13206998
]
Rajith Attapattu commented on QPID-3836:
----------------------------------------
The fix provided in QPID-3539 only works for the BURL format. This format
always declares a queue, so the above issue does not arise.
> no-local does not work for Qpid 0-10 JMS client
> -----------------------------------------------
>
> Key: QPID-3836
> URL: https://issues.apache.org/jira/browse/QPID-3836
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.12
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.15
>
>
> If no-local is set to true when create a consumer or a durable subscriber,
> messages published by the same connection should not be seen by this consumer.
> Currently due to a bug no-local is not passed correctly when creating the
> subscription queue.
> All though this works for Topics and Queues created when this information is
> available, not sure how this should be handled when subscribing to an already
> existing queue.
> AKAIK the no-local argument is passed on during queue-declare. Perhaps there
> is also a way to pass this on when creating a subscription ?
> (I will update the description when I find the answer to the above question).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
