You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2008/06/05 21:27:00 UTC
[jira] Commented: (CAMEL-578) JMX Instrumentation -
PerformanceCounter - last processed timestamp
[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43269#action_43269 ]
Claus Ibsen commented on CAMEL-578:
-----------------------------------
William good work.
I was wondering if you could take a look at the timing. It uses nano seconds but I am wondering why we divide the delta with 1000 when its passed to the performance counter.
counter.completedExchange((System.nanoTime() - startTime) / 1000);
And could the mbeans description be changed from usec to nano sec, as not everyone knows what a usec is.
And should we change to use the more common millis instead?
> JMX Instrumentation - PerformanceCounter - last processed timestamp
> -------------------------------------------------------------------
>
> Key: CAMEL-578
> URL: https://issues.apache.org/activemq/browse/CAMEL-578
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.3.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 1.4.0
>
> Attachments: jconsole.PNG, patch.txt
>
>
> Add a timestamp for the last completed exchange on the Camel JMX PerfformanceCounter.
> Its very nice to be able to see this information in the JMX console.
> And maybe add a first processed timestamp as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.