You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/05/28 18:36:04 UTC
[jira] [Updated] (CAMEL-11354) Optimise - JMX oldest inflight can
be optimised
[ https://issues.apache.org/jira/browse/CAMEL-11354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-11354:
--------------------------------
Summary: Optimise - JMX oldest inflight can be optimised (was: Optimise - JMX allow to turn off oldest inflight information)
> Optimise - JMX oldest inflight can be optimised
> -----------------------------------------------
>
> Key: CAMEL-11354
> URL: https://issues.apache.org/jira/browse/CAMEL-11354
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Fix For: 2.20.0
>
> Attachments: after.png, before.png
>
>
> Having to store timestamp per inflight exchange causes too much memory to be created as we create a key per exchange.
> See before.png
> If turning this off we dont have those extra objects
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)