[ 
https://issues.apache.org/jira/browse/QPID-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207008#comment-13207008
 ] 

Robbie Gemmell commented on QPID-3836:
--------------------------------------

I think the title is perhaps a little misleading, given the number of tests 
running that show it does work to an extent. Perhaps 'doesn't work when used on 
queues not originally declared no-local' would be clearer. The BURL usage may 
always send the queue declare, but redeclaring a queue that exists wont make it 
no-local.

The client currently only sends the no-local argument during queue creation as 
you mentioned, but there is support in the protocol for adding arguments to 
subscriptions so it could potentially be added there too (The protocol actually 
has a no-local field on the file and stream consume methods, so why it doesn't 
on the standard subscribe method I'm not sure)
                
> 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]

Reply via email to