Hi, I've encountered a scenario in a camel route involving (I believe) concurrency:
My route has a netty4 tcp consumer, which then uses a multicast to pass the message through a number of xsl transformers which then output to ActiveMQ endpoints. I've observed that when I receive a large XML message, followed almost immediately (approx. 1 millisecond) by a smaller XML message, the smaller message passes through the route before the large message (obviously to do with the cost of the transformation process). The order of the messages is important, so I'd like to control this behaviour. I'm trying to ensure that only one message is processed by the route at any given time, so would the solution be as simple as setting maxPoolSize=1 on the netty4 consumer? I'm having a hard time understanding the threading/concurrency model in camel, so can anyone help me with a good description somewhere of the lifecycle of a message through a camel route? Thank you in advance, Rob -- View this message in context: http://camel.465427.n5.nabble.com/Disabling-concurrency-in-camel-route-tp5786531.html Sent from the Camel - Users mailing list archive at Nabble.com.
