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 - User mailing list archive at Nabble.com.
