So far only JBM 1.4.4.GA (or 1.4.0.sp3-cp08 for EAP) supports that attribute. For AS 5.x you need to wait for the next release for it.
The JMS spec guarantees that messages sent from a particular producer are delivered in order to a single consumer in the absence of failures.
You don't need order grouping for that.
If you're not seeing that, please add a test case that demonstrates it and someone will investigate it since it would imply there is a bug.
Thanks for the quick response.
If there is only one consumer, the messages are coming in order. For e.g, if I use singleton MDB to consume the messages they are coming in order.
Since our requirement is to process bulk amount of messages, we are thinking of concurrently processing the messages. To achieve that, we are using multiple instances of the MDB's (using maxSession) to process the messages. Another approach which we followed was to create multiple bridges which consumes messages from the same queue. But we did not get the correct ordering in either of these approaches.
Is there a beta version of JBM available with 'EnableOrderingGroup' attribute which we can use for our testing?
Thanks again for the quick response