activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1103) STOMP "no-local" consumer not working
Date Sat, 08 Apr 2017 15:45:41 GMT


Justin Bertram commented on ARTEMIS-1103:

There's a handful of tests (e.g. {{org.apache.activemq.artemis.tests.integration.stomp.StompTest#testSubscribeToTopicWithNoLocal}})
that exercise the no-local feature for the STOMP implementation.  Those tests are all working
as far as I can tell.

Also, I looked at [the commit|]
related to ARTEMIS-979, and I can't see anything in it which would impact STOMP.  It's all
isolated to the OpenWire implementation.

Do you have a reproducible test you could share?  Perhaps your use-case is not covered in
our existing tests.

> STOMP "no-local" consumer not working 
> --------------------------------------
>                 Key: ARTEMIS-1103
>                 URL:
>             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
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:
> destination:jms.topic.TStompJMSBindingTests.TestNoLocal.Topic
> ack:auto
> id:{EF608581-10A2-432E-B938-131885A896B3}
> no-local:true

This message was sent by Atlassian JIRA

View raw message