Thanks James! I would say from the behavior I've been seeing that the RA is indeed ignoring the groupId.
I created 4 consumers on the queue, deleted the outbound MDB, and moved the message handling logic into the new class. When I do that, the grouping is indeed respected and messages arrive at the SOAP endpoint in the intended order! Yay. That's the good news. The bad news is that we really want to use MDBs. Any idea when the RA might become group aware? -John James.Strachan wrote: > > > The type of transport doesn't matter at all - vm, tcp or whatever. I'm > confident things would work fine if you just created, say, 100 > MessageListeners (each with their own session so they can support > parallel consuming). > > I'd definitely try make a simpler test case - taking out points of > complication which could affect the order (like having multiple EJBs > or parallel soap requests which could all break order). Given a number > of messages on the queue, placed in order with the same JMSXGroupID - > we should just test if the RA dispatches them in order. I've a feeling > the RA may ignore the message groups contract and parallelize the > dispatching to concurrent MDBs. > > -- > > James > ------- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/Groups-tf2952450.html#a8302770 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
