activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "clebert suconic (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (ARTEMIS-1834) Incorrect STOMP destination header
Date Thu, 17 May 2018 02:12:01 GMT

     [ https://issues.apache.org/jira/browse/ARTEMIS-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

clebert suconic closed ARTEMIS-1834.
------------------------------------

> Incorrect STOMP destination header
> ----------------------------------
>
>                 Key: ARTEMIS-1834
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1834
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: STOMP
>            Reporter: Lionel Cons
>            Assignee: Justin Bertram
>            Priority: Major
>             Fix For: 2.6.0
>
>
> In the most recent snapshot (2.6.0-20180427.020303-62) the STOMP {{destination}} header
is now modified by Artemis.
> I'm using {{anycastPrefix=/queue/}} and {{multicastPrefix=/topic/}} to match ActiveMQ
5's STOMP behavior.
> When sending a message to {{/topic/foo}}, the sent STOMP frame contains {{destination:/topic/foo}}
in its header, as expected.
> However, the received STOMP frame now contains {{destination:foo}} in its header. It
was {{destination:/topic/foo}} in previous Artemis versions.
> IMHO, the STOMP {{destination}} header should be left untouched. {{anycastPrefix}} and
{{multicastPrefix}} should only be used to guess the destination type and not to change the
destination string itself.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message