activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARTEMIS-1905) When using JMS API over STOMP protocol only multicast destinations are created
Date Mon, 04 Jun 2018 16:23:00 GMT

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

Justin Bertram updated ARTEMIS-1905:
------------------------------------
    Description: 
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.

{noformat}
SEND
destination:queue/foo

 text
{noformat}

It's possible to add {{destination-type}} header to the frame

{noformat}
SEND
destination:queue/foo
destination-type:ANYCAST

text
{noformat}

However, that is non-standard since there is no {{destination-type}} header defined in STOMP
protocol.

  was:
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.

 








 








 
 
 








 








 
 


> 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
>            Priority: Major
>
> 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.
> {noformat}
> SEND
> destination:queue/foo
>  text
> {noformat}
> It's possible to add {{destination-type}} header to the frame
> {noformat}
> SEND
> destination:queue/foo
> destination-type:ANYCAST
> text
> {noformat}
> However, that is non-standard since there is no {{destination-type}} header defined in
STOMP protocol.



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

Mime
View raw message