I understand that the aggregator's messages do not count - they are checked out during shutdown just fine.
The problem is the 'direct:testInput' route is actively processing a message (represented by the delay(2*1000)), but the DefaultShutdownStrategy does not count this message. It begins shutting down routes, starting with the 'direct:testInput', then 'direct:testOutput'. When the message is finally done processing, it has no where to go and throws an exception. The desired behavior would be to allow this message to finish processing and get to the aggregator before calling prepareShutdown and shutdown, then the normal shutdown would work fine. Is this possible? -- View this message in context: http://camel.465427.n5.nabble.com/Calculation-of-in-flight-messages-in-DefaultShutdownStrategy-tp5747034p5747683.html Sent from the Camel - Users mailing list archive at Nabble.com.