camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (CAMEL-3631) Graceful shutdown - Add logic to detect slow/hung in-flight exchanges
Date Sat, 23 Apr 2011 07:31:06 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023520#comment-13023520
] 

Claus Ibsen edited comment on CAMEL-3631 at 4/23/11 7:30 AM:
-------------------------------------------------------------

Its just a reference to the Exchange you put in the Map, so it wont eat up memory. However
it would do it anyway and thats because of the defensive copy nature in the Camel routing
engine (scheduled to be improved in Camel 3.0). The reference stored in the Map would be for
the input Exchange. And because of the routing engine would defensively copy to a new Exchange
during routing, that reference eat up memory pointing to the input Exchange (which otherwise
could get GC'ed). 

So I actually suggest to move this ticket to be resolved after we have improved the routing
engine, to avoid the defensive copy of the Exchange during routing.


      was (Author: davsclaus):
    Its just a reference to the Exchange you put in the Map, so it wont eat up memory. However
it would do it anyway and thats because of the defensive copy nature in the Camel routing
engine (scheduled to be improved in Camel 3.0). So I actually suggest to move this ticket
to be resolved after we have improved the routing engine, to avoid the defensive copy of the
Exchange during routing.
  
> Graceful shutdown - Add logic to detect slow/hung in-flight exchanges
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-3631
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3631
>             Project: Camel
>          Issue Type: Improvement
>    Affects Versions: 2.6.0
>            Reporter: Claus Ibsen
>            Assignee: Ashwin Karpe
>             Fix For: 3.0.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: http://www.atlassian.com/software/jira

Mime
View raw message