camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashwin Karpe (JIRA)" <>
Subject [jira] [Commented] (CAMEL-3631) Graceful shutdown - Add logic to detect slow/hung in-flight exchanges
Date Sat, 26 Mar 2011 01:21:05 GMT


Ashwin Karpe commented on CAMEL-3631:


Please be aware that the logUndeliveredInflightExchanges() code is commented. This patch is
not intended for commit. I will uncomment the code of course when I have your comments and
feedback. Obviously, I will add unit tests as well. I am working on them right now...



> Graceful shutdown - Add logic to detect slow/hung in-flight exchanges
> ---------------------------------------------------------------------
>                 Key: CAMEL-3631
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>    Affects Versions: 2.6.0
>            Reporter: Claus Ibsen
>            Assignee: Ashwin Karpe
>             Fix For: 2.8.0
>         Attachments: Camel-3631.patch
> 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.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message