I think you have some "read ahead" (prefetching) going on. I've seen that happening such that a consumer doesn't just read "the next" msg, but reads in a bunch and holds them for the consuming process. You should be able to limit that behavior with a property setting.
-- View this message in context: http://camel.465427.n5.nabble.com/Two-Camel-Configs-Polling-Same-IBM-MQ-Only-one-picking-the-message-tp5800355p5800367.html Sent from the Camel - Users mailing list archive at Nabble.com.
