[ARTEMIS-948] SockJS clients are not receiving messages when published to queues

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Invalid
• Affects Version/s: 1.5.2
• Component/s: STOMP

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/

• Assignee: Unassigned
• Reporter: Paul Gobin
• Created: 07/Feb/17 23:11
• Updated: 10/Mar/17 13:45
• Resolved: 08/Feb/17 20:19

Description

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/