Hi Rob, I got around to doing some testing on the multi-queue consumer feature you added. So far things have looked good mostly, but there is one issue I've run into and would like your help on.
When we had single-queue consumers, we had fair allocation behavior across queues, in the sense that if I have 2 queues A and B, each with 100 messages, and one JMS session having a listening consumer on queue A and a listener on queue B, the message processing order will be round robin -- i.e., M_A_1 (representing the first message on queue A), M_B_1, M_A_2, M_B_2, M_A_3, M_B_3, and so on. But now, if I run the same test with the session having a single multi-queue consumer on A and B instead, the order is, roughly, first the 100 messages on A, followed by the messages on B (only a few B messages are processed before all A messages are done). I enqueue the messages in the round robin order. I've also tried this with synchronous receives from both queues instead of asynchronous listening, and I see similar behavior. Is there any way we can mimic the "fair" behavior of single-queue consumers with multi-queue consumers? Thanks, Helen
