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

Paul Gobin updated ARTEMIS-948:
-------------------------------
    Environment: 
Reference to 
http://stackoverflow.com/questions/31688222/best-way-to-automatically-add-stomp-native-headers-to-headers

When sending messages to dynamically created destinations example  
jms.queue.osportal.chat.DEV.userListOnline, the expected behavior is that the 
Stomp over SockJS browser client should receive the message since they are 
subscribed to said destination. Using JConsole, the destination is not listed 
and the browser client is not receiving the messages, works with ActiveMQ and 
Apollo except the predicate used for ActiveMQ and Apollo is /topic/ and /topic/


  was:
Reference to 
http://stackoverflow.com/questions/31688222/best-way-to-automatically-add-stomp-native-headers-to-headers

When sending messages to dynamically created destinations example  
jms.queue.osportal.chat.DEV.userListOnline, the expected behavior is that the 
Stomp over SockJS browser client should receive the message since they are 
subscribed to said destination. Using JConsole, the destination is not listed.



> SockJS clients are not receiving messages when published to queues
> ------------------------------------------------------------------
>
>                 Key: ARTEMIS-948
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-948
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>          Components: Stomp
>    Affects Versions: 1.5.2
>         Environment: Reference to 
> http://stackoverflow.com/questions/31688222/best-way-to-automatically-add-stomp-native-headers-to-headers
> When sending messages to dynamically created destinations example  
> jms.queue.osportal.chat.DEV.userListOnline, the expected behavior is that the 
> Stomp over SockJS browser client should receive the message since they are 
> subscribed to said destination. Using JConsole, the destination is not listed 
> and the browser client is not receiving the messages, works with ActiveMQ and 
> Apollo except the predicate used for ActiveMQ and Apollo is /topic/ and 
> /topic/
>            Reporter: Paul Gobin
>            Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to