Return-Path: 
 <users-return-41487-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id BF6311090C
	for <apmail-camel-users-archive@www.apache.org>;
 Fri,  2 Aug 2013 08:18:24 +0000 (UTC)
Received: (qmail 14952 invoked by uid 500); 2 Aug 2013 08:18:23 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 14693 invoked by uid 500); 2 Aug 2013 08:18:23 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 14685 invoked by uid 99); 2 Aug 2013 08:18:22 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Aug 2013 08:18:22 +0000
X-ASF-Spam-Status: No, hits=0.6 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.219.42 as permitted sender)
Received: from [209.85.219.42] (HELO mail-oa0-f42.google.com) (209.85.219.42)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Aug 2013 08:18:17 +0000
Received: by mail-oa0-f42.google.com with SMTP id i18so772832oag.1
        for <users@camel.apache.org>; Fri, 02 Aug 2013 01:17:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=DQnuNDXGjEQzLlzCjoaVovTS7mPC0N7HY8TJf+5h7HE=;
        b=wsFz/KrskgxxMZe3JIjkDYuKP8gug2QoxhMy54ayqTNFGd/uIFddu5KGiIAhoCFjfZ
         HNYJVTGiT8WoPOWxdXzqO/G94/yv0fBwRCjVz+jbADYqbSw3lFgGgtc3wookP5xca+dL
         ayyTh6tobuSi+wGNsYyz55lJYrPwHFRyQL6jGD9VJ/4mzrYOepMadK+Wcoxms9jwcx5C
         atfi0el4RKM84eSfXSv0w/jboZ17XejtsAP7WxH1QlVJh/fWVXJrXDFpvlnyoIDbzY6n
         hQEnqqvncbv53xS463qpdzmo8JutTEyjLCIEEon7gRqKGADXXRxsx1H9lPHpZaroONUf
         9mIQ==
X-Received: by 10.50.23.103 with SMTP id l7mr164530igf.14.1375431476907; Fri,
 02 Aug 2013 01:17:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.233 with HTTP; Fri, 2 Aug 2013 01:17:36 -0700 (PDT)
In-Reply-To: <1375403464134-5736667.post@n5.nabble.com>
References: <1284744197479-2844045.post@n5.nabble.com>
 <AANLkTikhO8ZKCMU9NWWm73LkSEQTtKMvEE3nc+E9ERJA@mail.gmail.com>
 <1375136422393-5736458.post@n5.nabble.com>
 <CAGB5yNmqXfte7AZpRndbPPD8qZ9NZAjH+eQpRXTVoSaVv5YpgA@mail.gmail.com>
 <1375403464134-5736667.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Fri, 2 Aug 2013 10:17:36 +0200
Message-ID: 
 <CAGB5yNkH-=uV=dX7ej2NfQS4X8VXG9qytbP+SCr_wm0x2-1Yeg@mail.gmail.com>
Subject: Re: best practice for logging execution time
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

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