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] [Commented] (ARTEMIS-948) SockJS clients are not receiving messages when published to queues
Date Wed, 08 Feb 2017 01:59:42 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857228#comment-15857228
] 

Justin Bertram commented on ARTEMIS-948:
----------------------------------------

Couple of questions:

# What is triggering the creation of the destination?  Is it a producer sending a message
or consumer being created?
# If JConsole doesn't list the destination how do you know it is being created?
# Do you want "topic" semantics?  If so, why are you using a destination prefixed with "jms.queue."
(which will have queue semantics)?
# Do you have a reproducible test-case you could provide?

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



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

Mime
View raw message