On 3/28/07, osian <[EMAIL PROTECTED]> wrote:
This has now been rectified, it was a bug in how the JMSXMessageGroupID was
being generated, now that it is generated properly, all is well,
Great, thanks for letting us know!
--
James
---
http://radio.weblogs.com/0112098/
This has now been rectified, it was a bug in how the JMSXMessageGroupID was
being generated, now that it is generated properly, all is well,
Thanks,
Osh
--
View this message in context:
http://www.nabble.com/Out-Of-Order-Message-Processing-tf3446025s2354.html#a9708365
Sent from the ActiveMQ
On 3/22/07, osian <[EMAIL PROTECTED]> wrote:
I have noticed that for 2 of the sets of messages, the JMSXGroupID was
generated slightly differently, because they didn't have as much information
as the other messages, I am amending this, and running the test again. But,
with this in mind, these m
were processed
first, before the other messages.
Is this correct that it does this, and is there any way of protecting
against this?
Osian
--
View this message in context:
http://www.nabble.com/Out-Of-Order-Message-Processing-tf3446025s2354.html#a9610598
Sent from the ActiveMQ - User mailing list archi
Note, that when I have 1 or more consumers running, then the message
ordering is fine.
Is this a known issue, or is there some configuration that needs to be
setup?
Thanks in advance,
Osian
--
View this message in context:
http://www.nabble.com/Out-Of-Order-Message-Processing-tf3446025s2354
