You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Tom Ross (JIRA)" <ji...@apache.org> on 2018/06/04 12:18:00 UTC
[jira] [Created] (ARTEMIS-1905) When using JMS API over STOMP
protocol only multicast destinations are created
Tom Ross created ARTEMIS-1905:
---------------------------------
Summary: When using JMS API over STOMP protocol only multicast destinations are created
Key: ARTEMIS-1905
URL: https://issues.apache.org/jira/browse/ARTEMIS-1905
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Broker, STOMP
Affects Versions: 2.6.0
Reporter: Tom Ross
Assignee: Justin Bertram
When calling JMS API createQueue() only multicast destinations are created in the broker back end. The call to createQueue() should result in a anycast destination to be created.
Also when sending a frame like would result in multicast destination.
"SEND\n" +
"destination:queue/foo\n" +
"\n" +
text +
END_OF_FRAME;
It's possible to add destination-type header to the frame
"SEND\n" +
"destination:queue/foo\n" +
"destination-type:ANYCAST\n" +
"\n" +
text +
END_OF_FRAME;
but that is non standart since there is no destination-type header defined in STOMP protocol.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)