Thank you four your ideas, Claus. We need the "asyncConsumer=true" setting as it dramatically boosts our performance (the broker already delivers the messages unsorted, so we have to re-order them anyway).
But a route policy should do the trick - I have already thought about implementing a RoutePolicy to turn off the JMS consumer in some cases (The processed JMS messages are buffered in a database, another camel route is used to fetch & aggregate them. If there are many messages in the JMS queue, we sometimes experience the problem that database reads are blocked by the write operations of the JMS consumer until the traffic decreases - so for periods of high traffic, it could be useful to disable the JMS consumer from time to time to give the database consumer the chance to kick in) So - RoutePolicy, here we go! Thank you, Joerg -- View this message in context: http://camel.465427.n5.nabble.com/Limit-number-of-JMS-messages-when-processing-asynchronously-tp5774822p5774828.html Sent from the Camel - Users mailing list archive at Nabble.com.
