[
https://issues.apache.org/jira/browse/CAMEL-13587?focusedWorklogId=249304&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-249304
]
ASF GitHub Bot logged work on CAMEL-13587:
------------------------------------------
Author: ASF GitHub Bot
Created on: 28/May/19 12:32
Start Date: 28/May/19 12:32
Worklog Time Spent: 10m
Work Description: bdevido commented on pull request #2949: Camel 2.x -
CAMEL-13587 backporting from master
URL: https://github.com/apache/camel/pull/2949
CAMEL-13587: Inflight repository browse should compute elapsed if themessage
is still inflight at a given node. Thanks to Barbara De Vido for reporting.
Backporting from master
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 249304)
Time Spent: 10m
Remaining Estimate: 0h
> InflightRepository, InflightEntry getElapsed is 0
> -------------------------------------------------
>
> Key: CAMEL-13587
> URL: https://issues.apache.org/jira/browse/CAMEL-13587
> Project: Camel
> Issue Type: Bug
> Components: came-core
> Affects Versions: 2.22.1
> Environment: Camel 2.22.1
>
> Reporter: Barbara De Vido
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
> Attachments: image-2019-05-27-17-04-12-319.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Hi,
> I made a camel-route that checks about inflight messages on other server
> through JMX connection.
> It was working fine in 2.17.x but now we upgrade to 2.22.1 and I always
> obtain a result of 0 millisecond for the elapsed field.
> I use the browse() operation of JMX bean. You can use jconsole to run a
> simple test.
> !image-2019-05-27-17-04-12-319.png!
> This is a major bug for us, since we use the code to monitoring production
> routes. Is there any workaround like get the echange historymessage from the
> exchage id?
> Thank you
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
