That's easy - Queue semantics. I recommend reading the JMS specification
with a focus on understanding how Queues and Topics operate.
With that said, let me clarify. Queues guarantee once-and-only-once message
delivery (with some caveats related to ensuring clients actually processed
messages).
I should say this behavior is also seen in the supplied demo websocket app.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Wierd-skipping-of-messages-using-Websocket-activeMQ-tp4680230p4680246.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
