Thank you for your speedy response. In answer to your questions: I have read that document, but in this case I only want to shut down Route #2. When Route #1 picks up the next file I want to to dynamically create a new (uniquely named) Route #2, but routes #1, #3 and #4 can (hopefully) remain unaffected.
Routes #3 and #4 are one way (InOnly). I have not specified an aggregation strategy for the splitter, because I have no desire to aggregate the messages after they are split. I'm not sure in which route the in-flight messages are remaining, however as I am only attempting to shut down route #2, is it too naive to assume it must be that route? Or does the act of shutting down Route #2 also attempt to shut down other routes? I suppose the question I am unsure of is, why are there still inflight messages? I know the messages have been sent to jms, as I can see them on the queue, should this not remove them from flight? -- View this message in context: http://camel.465427.n5.nabble.com/Shutting-down-a-route-inflight-messages-and-splitter-tp5735716p5735723.html Sent from the Camel - Users mailing list archive at Nabble.com.
