[jira] [Closed] (ARTEMIS-948) SockJS clients are not receiving messages when published to queues

["Martyn Taylor (JIRA)" <ji...@apache.org>]

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

Martyn Taylor closed ARTEMIS-948.
---------------------------------

> 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
>
> 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 /queue/



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