[
https://issues.apache.org/jira/browse/ARTEMIS-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962153#comment-15962153
]
Michael Justin commented on ARTEMIS-1103:
-----------------------------------------
I found that the test case did not fail because of an unexpected message, so I
close this issue.
What actually happened: my unit test verified that no message arrived from the
opic. And then, it created another consumer without the no-local flag and
retried to receive a message. This failed with pre-2.0 versions of Artemis, but
with 2.0 a message was received. It looks like pre-2.0 versions swallowed the
message when the consumer tried to receive it, while 2.0 kept it until the next
consumer (without no-local) tried to receive a message.
> STOMP "no-local" consumer not working
> --------------------------------------
>
> Key: ARTEMIS-1103
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1103
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: STOMP
> Affects Versions: 2.0.0
> Reporter: Michael Justin
> Assignee: Justin Bertram
>
> In Artemis 2.0.0, adding a no-local:true header doesn't work, meaning the
> client can still receive messages from the same connection.
> (the changes made to fix OpenWire no-local support in
> https://issues.apache.org/jira/browse/ARTEMIS-979 might be related)
> In previous versions (tested with Artemis 1.5.1 and 1.5.4) setting the
> no-local flag had the expected effect.
> Example STOMP frame with no-local header set to true:
> SUBSCRIBE
> destination:jms.topic.TStompJMSBindingTests.TestNoLocal.Topic
> ack:auto
> id:{EF608581-10A2-432E-B938-131885A896B3}
> no-local:true
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
