[
https://issues.apache.org/jira/browse/CAMEL-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025291#comment-13025291
]
Ashwin Karpe commented on CAMEL-3631:
-------------------------------------
Hi Claus,
Ok... no worries. I was afraid of these copies and have been burnt by it when
using ProducerTemplates to push exchanges to several different destinations
using a cache. I was hence very wary of this and implemented my solution the
way I did.
I do take you point and if you think this is best implemented after improving
the routing engine, then I am happy to stop further work on this issue for the
time being.
Cheers,
Ashwin...
> 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
