[
https://issues.apache.org/jira/browse/CAMEL-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336638#comment-14336638
]
Claus Ibsen commented on CAMEL-8385:
------------------------------------
I am not sure that JMX attributes should invoke computing logic, but instead be
no overhead return field values.
So IMHO it would be better to have logic in the inflight registry that keeps
state of the oldest per route and keeps that list up to date when an exchange
is done. And then the route mbeans can quickly read that information from the
inflight registry without causing computation overhead.
Also the current approach would imho cause to much overhead if users have many
routes, and then some jmx tools read all the attributes, which per route causes
the "computing".
And its okay to add / change the interface in a new minor release such as Camel
2.15. We add the api changes in the release notes.
> Add a OldestInflightStartedTimestamp and OldestInflightStartedExchangeId
> attribute to route MBeans
> --------------------------------------------------------------------------------------------------
>
> Key: CAMEL-8385
> URL: https://issues.apache.org/jira/browse/CAMEL-8385
> Project: Camel
> Issue Type: Bug
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 2.15.0
>
>
> If we has an attribute like OldestInflightStartedTimestamp and
> OldestInflightStartedExchangeId then it would be easier to monitor for routes
> which get 'stuck' or exceed the expected SLA for the route to complete
> processing the exchange.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
