[CAMEL-3631] Graceful shutdown - Add logic to detect slow/hung in-flight exchanges

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Later
• Affects Version/s: 2.6.0
• Fix Version/s: 3.0.0
• Assignee: Ashwin J. Karpe
• Reporter: Claus Ibsen
• Created: 05/Feb/11 13:01
• Updated: 02/May/13 02:29
• Resolved: 28/Apr/11 17:25

Description

We should improved the graceful shutdown to be more verbose and provide more detailed information when it appears in-flight exchange(s) appear to be hung.

We have the created timestamp on the exchange, and if we let in flight repo, track each exchange, then we can grab the exchange and thus know how long time it currently has been in-flight. And then if the time is > threshold, we can output that in the logs.

It requires the in flight registry now also keep track of each exchange. We may consider this as an optional feature you should enable, as it requires us to put/remove Exchange into a ConcurrentMap to keep track of each exchange.

Issue Links

• depends upon: CAMEL-1817 Moved logic for defensive copy of current exchange from Pipeline to RedeliveryErrorHandler