Thanks Rob, was afraid that was the case. We built a system with mixed asynchronous and synchronous consumers using AMQP 0-10. Most of the time, messages are consumed asynchronously. But if we dequeue a "bulk" message, we create a new session to consume multiple messages synchronously but wrap the acknowledgement/dequeue in the context of a single transaction. Unfortunately, it sounds like delivery and acknowledgement goes hand-in-hand with AMQP 0-91 so "bulk" consume is no longer possible.
A couple of quick questions from your reply in the other thread (sorry for jumping around) http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-td6934582i20.html > It may be possible to code a client library side change without changing > the broker (basically reduce consumer credit to 0 as soon as one consumer > has a message, and release any messages that have been prefetched), but > that probably isn't a trivial piece of work. We might start looking into this as a short term solution. Is it easier to try on an older client (i.e. v0.16)? > Meanwhile I've also knocked up an implementation of the "single consumer > across many queues" idea that I floated the other day. That won't make it > into 0.30 (it's currently only on my laptop), but I would hope it would be > in 0.32, or whatever the next release is called. Note that this change > will require both a new client and a new broker, but should also be easily > available from all the other 0-10 clients. If there is plans to release this in v0.32/trunk, we will be super eager to test it out :) Cheers! Dan -- View this message in context: http://qpid.2158936.n2.nabble.com/Synchronous-consumer-can-only-dequeue-1-message-in-AMQP-0-91-tp7613017p7613067.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
