camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: best practice for logging execution time
Date Fri, 02 Aug 2013 08:17:36 GMT
The JMX stats is per Exchange in the processor nodes.
There is JMX stats per route as well which would then be "per route"
And likewise a JMX stats for the entire CamelContext.

So you have 3 different levels of stats.


So in your aggregate route, you will have stats for all incoming
exchanges into the aggregator.
And stats for the outgoing. So you can have 10 incoming, and 1 outgoing exchange




On Fri, Aug 2, 2013 at 2:31 AM, salemi <salemi@avaya.com> wrote:
>
>
> I have the following route and aggregating the 10 Exchanges into one. Now
> when I run Camel JMX and it provides mewith the meanProcessingTime. What
> does that mean for the route below. Is  the mean time for a exchange that
> contains 10 exchanges or for each exchange that arrives trough JMS?
>
> <route>
> <from uri="jms:topic:topic1">
> <unmarshal ref="csJSON"/>
> <to uri="direct:javaspaces"/>
> <route>
>
> <route id="javaspaces" shutdownRunningTask="CompleteCurrentTaskOnly"
> autoStartup="true">
> <from uri="direct:javaspaces"/>
> <transacted/>
> <aggregate strategyRef="aggregatorStrategy" completionSize="10"
> completionTimeout="1000">
> <correlationExpression>
> <simple>${body.entity}</simple>
> </correlationExpression>
> <bean ref="jsInterface"/>
> </aggregate>
> </route>
>
>
>
>
>
> -----
> Alireza Salemi
> --
> View this message in context: http://camel.465427.n5.nabble.com/best-practice-for-logging-execution-time-tp2844045p5736667.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Mime
View raw message