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).