Thanks a lot for your reply; now, it makes sense. I just have one question
concerning your last point; I didn't understand why JMS groups can create
lots of problems? In your opinion, we should not use it?
Thank you,
Rosy
--
View this message in context:
http://activemq.2283324.n4.nabble.com
If there are multiple consumers, having each consumer reject out-of-order
messages as Art suggested is only going to work if you use message groups,
so take his last paragraph as good general advice but ignore it if you
choose to implement the rest of his suggestions.
But if you're using message g
Hey Rosy - ActiveMQ is a messaging solution, primarily focused on getting
messages from producers to consumers. Advanced logic of that type really
belongs in an application. There's no straight-forward way to add that to
ActiveMQ itself, and it would be difficult to diagnose if such functionality
Hello,
I'm facing the same issue.
Is there an option on Active MQ level to preserve the order of execution of
messages in case of an exception? . In other words, assume that we have
inside message ID=1 info about an object called student having for example
ID=Student_1000 and this message failed a
That feature does not exist. It would also be tricky to implement as
ActiveMQ stores messages for serial access, not random access.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-broker-automatically-move-messages-with-same-JMSXGroupID-to-DLQ-tp4685943p4685950.
