You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Lionel Cons (JIRA)" <ji...@apache.org> on 2018/04/27 07:44:00 UTC
[jira] [Created] (ARTEMIS-1834) Incorrect STOMP destination header
Lionel Cons created ARTEMIS-1834:
------------------------------------
Summary: Incorrect STOMP destination header
Key: ARTEMIS-1834
URL: https://issues.apache.org/jira/browse/ARTEMIS-1834
Project: ActiveMQ Artemis
Issue Type: Bug
Reporter: Lionel Cons
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)