[
https://issues.apache.org/jira/browse/QPID-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPID-1850.
----------------------------------
Resolution: Fixed
Resolving this, nolocal defiitely works at the connection level now so this was
fixed at some point long long ago.
> nolocal is mishandled.
> -----------------------
>
> Key: QPID-1850
> URL: https://issues.apache.org/jira/browse/QPID-1850
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.5, 0.6
> Reporter: Aidan Skinner
>
> TopicSession.createSubscriber() does not handle the noLocal parameter
> properly. Setting noLocal to true should (according to the JMS spec) prevent
> delivery of a message to a subscriber listening on the same connection as was
> used to publish the message. However, in QPID, setting noLocal to true
> prevents delivery of the message at all to the same clientid.
--
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]
