Hi Rob, in case you are interested, wanted to give you an update from our side. First, let me begin by saying how awesome the Qpid community has been. Your patience and responsiveness in addressing our questions is way beyond what we could have hoped for from this community. I think I speak for Salesforce in saying that we owe you a couple rounds of beer, in case you are ever bored and in San Francisco :)
Our plan is to address per-consumer prefetching on the v0.16 clients we currently run in production using the suspend & release prefetched messages approach described above. The general flow of our solution is as follows: 1) Each time a message is dispatched and onMessage is invoked, we register the parent Qpid session with a session tracker 2) The session tracker is scheduled every x seconds and looks for Qpid sessions that is processing a long running messages 3) Once the session tracker finds a long running message, it invokes "sendSuspendChannel" and "rejectMessagesForConsumerTag" on the session to suspend dequeue and release any prefetched messages 4) When the long running message is completed, it unregisters the parent Qpid session from the session tracker and invokes "sendSuspendChannel" to resume dequeue We are in the process of performance testing this solution to make sure that a) overhead of suspend and release is manageable and b) no anomalies arise from repeatedly suspending and unsuspending the session For our long term plan, we plan to upgrade to the latest version of the client/broker and use the single-consumer-multiple-queue feature you've built in v0.32 for AMQP 0-10. After we've patched our v0.16 client, we plan to focus on vetting this. We are also abandoning efforts to switch to per-session prefetch with AMQP 0-91. We are grateful for bulk dequeue support in AMQP 0-91, but in subsequent testing, we encountered other incompatibilities due to our use case. (Unfortunately have not had time to dig further). Given that the v0.16 band-aid solution eliminated the immediate urgency, we feel that taking the time to build a solution around AMQP 0-10 is the right approach going forward. By the way, what is the typical release time frame for Qpid (with v0.32/trunk in mind)? Cheers, Dan -- View this message in context: http://qpid.2158936.n2.nabble.com/Re-1-Queue-with-2-Consumers-turn-off-pre-fetching-tp6934582p7613381.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
