My reading of the JMS spec and common implmentations/user expectations would be the same as Rob's - i.e. the message order is not the only characteristic used to define group support.
In JMS, the sequence id would be used to maintain order, but the expectation is that the group are processed as a whole on receipt of the final message in the group rather than simply shared out between consumers and processed in order. Marnie On Mon, Jun 27, 2011 at 8:00 PM, Gordon Sim <[email protected]> wrote: > On 06/27/2011 07:58 PM, Gordon Sim wrote: > >> For most applications however I believe you can still keep the strict >> ordering even allowing for 'requeuing' due to rollback or connection >> failure. >> > > Where you want the stronger guarantee that a message is not even delivered > until all preceding messages in the group are accepted the clients can set a > prefetch of 1 for that queue. > > > ------------------------------**------------------------------**--------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: > mailto:dev-subscribe@qpid.**apache.org<[email protected]> > >
