There is no ordering guarantee in this case, as each destination will do an independent dispatch. Ordering is per destination only so messages from C and D will be interleaved.
When there are a pool of consumers, by default dispatch will round robin push to each consumer. You can change this behavior with the strictOrderDispatch policy entry, so messages in order will be pushed up to the prefetch limit. On 16 May 2012 10:05, mwessel <maiko.wes...@bwessel.de> wrote: > I have a question concerning the consumption process on hierarchical queues > in combination with wildcards. > > Defined Queues: "A.B.C.D" > Subscribers subscribes to "A.B.>" > > Now messages are published to C and D. > > In which order does the subscriber receive the messages? > First all messages from C and then D? > > What happen when a pool of subscriber exists? > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Consumption-order-on-hierarchical-queues-using-wildcards-tp4641049.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://fusesource.com http://blog.garytully.com
