anchor.diff:  Notice that suppression is _a best effort_ attempt and there may still be some
   logging from 3rd party libraries, which Camel cannot control.
   
  -== Logging inflight exchange information on timeout
  +=== Logging inflight exchange information on timeout
   
   If a graceful shutdown could not shutdown cleanly within the given
   timeout period, then Camel performs a more aggressive shutdown by
  
positive.code: consumer to complete all the tasks (messages) before shutting down. For
  example a xref:components::file-component.adoc[File] consumer will process all the pending
  files it has picked up before shutting down.
  
  == JMX managed
  
  The `ShutdownStrategy` is JMX aware, so you can manage it from a
  JMX console. This allows to adjust the strategy at runtime, such as changing the timeout setting.
  
  == Stop individual routes
  
  
negative.code: context.getShutdownStrategy().setLogInflightExchangesOnTimeout(false);
  ---------------------------------
  
  === JMX managed
  
  The `ShutdownStrategy` is JMX aware, so you can manage it from a
  JMX console. This allows to adjust the strategy at runtime, such as changing the timeout setting.
  
  == Controlling ordering of routes
  
  You can configure the order in which routes should be started, and thus
  