[
https://issues.apache.org/jira/browse/CAMEL-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14330322#comment-14330322
]
Claus Ibsen commented on CAMEL-8385:
------------------------------------
There is already an inflight registry which can give you that information.
See
org.apache.camel.api.management.mbean.ManagedInflightRepositoryMBean
And it has more details, so you can see where the message "is stuck". It has a
nodeId which is the current node, etc.
> 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)
