So I got a chance to look at this again and I think the root cause is an issue with how the AggregateProcessor responds to prepareShutdown. I think it responds correctely, but the DefaultShutdownStrategy does not consider the fact that doing the prepareShutdown routine may actually spawn more messages coming out of some services like the AggregateProcessor.
Take a look at https://github.com/chessami92/camel/compare/camel-2.13.x...features%2Fbetter-route-shutdown-deferral to see the test that I added and how I fixed the problem in the DefaultShutdownStrategy and let me know what you think. I can do a pull request if you think this is something that should be included in camel core. I know there isn't a bug for it out there, so let me know if I need to make one first, or if you even consider this behavior a bug. -- View this message in context: http://camel.465427.n5.nabble.com/Calculation-of-in-flight-messages-in-DefaultShutdownStrategy-tp5747034p5750935.html Sent from the Camel - Users mailing list archive at Nabble.com.
