can camel throttle messages based a dynamic message key?

I have a route that is invoked to get a status of an object "foo". The instance of foo is identified by a key. Concurrently at any given time I may receive following requests on the camel route: GET status of foo/@id=A12 GET status of foo/@id=A12 GET status of foo/@id=A12 GET status of foo/@id=A

transacted and split camel route does not invoke onException

I have a route that is transacted and split. The split calls a separate route to get some data via a CXF endpoint. When the CXF endpoint returns with an exception, the split group will stop but the exception never makes it into the onException handler of the split route. All the documentation and f

Re: recipientList together with UseLatestAggregationStrategy results in original in message to be returned

Hi Claus, Yes I explicitely specified InOut on all the exchanges involved but that did not make a difference. The real problem here is, it sometimes works and sometimes does not. I also observed a similar behaviour that I can reproduce somewhat more consistently that involves a CXF Endpoint, direct

recipientList together with UseLatestAggregationStrategy results in original in message to be returned

I am using the recipientList to forward a message to a dynamic vm:// endpoint. I also enabled parallel processing and specified the UseLatestAggregationStrategy in the hope to get the response message from the last consumer. However what I observe is that the message is sent to the dynamic recipie