It turned out to be a bug in the stomp client I was using (stompjs for nodejs). When I switched to another nodejs stomp client ( stomp-client for nodejs), it worked fine. Using stompjs client cost me 5 days of extra time.
-- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-fails-to-deliver-message-to-Stomp-consumer-tp4675273p4675310.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
