allthingssecurity commented on PR #28805: URL: https://github.com/apache/camel/pull/28805#issuecomment-6575208213
@oscerd thanks for the review. Both confirmed: 1. Yes, it is intentional. `routesOrdered` is `routes` sorted by startup order (reversed when `shutdownRoutesInReverseOrder`), and the graceful path already shut down in that order. On main the timeout path logged the inflight exchanges and forced `prepareShutdown` in the caller's order instead, so the forced path can now differ from the graceful one only in being correct. 2. Yes. With overlapping shutdowns, `isTimeoutOccurred()` and `getCurrentShutdownTaskFuture()` are best-effort "last writer" values for monitoring and for the existing callers. Each `doShutdown` decides on its own local future and flag, which is what fixes the cross-talk. _Claude Code on behalf of allthingssecurity_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
