Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.218.211 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=PJ/TsY8Avhw439dfXo1fF6IfMtq7qUAiKdNb7yl8dbuKhCjzgRN1hUjGM6PYcr/7bO
         Q9KAwTCFGyJyfs8N33skncMCEwPBme0TrOZea5Q30JEZIsgKXto8UhQwxCABbqvFDHJn
         JWe5EGCQDUcdrRndUme81cLyGi7fBCrK0swRw=
MIME-Version: 1.0
In-Reply-To: <26873948.post@talk.nabble.com>
References: <26873948.post@talk.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Mon, 21 Dec 2009 15:04:19 +0100
Message-ID: <5380c69c0912210604x7311320cw1027d82f34f5d125@mail.gmail.com>
Subject: Re: How does an aggregator behave with multiple consumers?
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 21, 2009 at 2:27 PM, ee7arh <andrew.hurst@2e-systems.com> wrote=
:
>
> Hi,
>
> When you have a route with mutliple concurrent consumers and this route
> contains an aggregator, does the aggregator aggregate messages from all
> consumer threads or is there in effect a separate aggregator per consumer
> thread?
>
> I have following route which is currently set to 1 concurrentConsumer. Ca=
n I
> safely increment this to a higher value knowing that all messages which g=
o
> through the route will be aggregated together as necessary or does each
> concurrent consumer start it's own aggregator in which case a total redes=
ign
> is required?
>
> =A0from("activemq:queue:NotificationsToSend?maxConcurrentConsumers=3D1&co=
ncurrentConsumers=3D1")
> =A0=A0 =A0 =A0 =A0 =A0 =A0.to("bean:" + NotificationsHandler.serviceName =
+
> "?method=3DsendNotification")
> =A0=A0 =A0 =A0 =A0 =A0 =A0.to("bean:" + NotificationsHandler.serviceName =
+
> "?method=3DsaveNotificationData")
>
> =A0=A0 =A0 =A0 =A0 =A0 =A0// Aggregate by IdHeader to group the exchanges=
 together
> =A0=A0 =A0 =A0 =A0 =A0 =A0.aggregate(header("IdHeader"), new
> GroupedExchangeAggregationStrategy())
>
> =A0.completionPredicate(header("aggregated").isEqualTo(header(Handler.EXP=
ECTED_NOTIF_HEADER)))
>
> =A0=A0 =A0 =A0 =A0 =A0 =A0// Update the notification status accordingly
> =A0=A0 =A0 =A0 =A0 =A0 =A0.to("bean:" + SchedChgHandler.serviceName +
> "?method=3DupdateNotificationStatus");
>
> Thanks and BRegards
> Andrew
>

Hi

You can ask the computer :) And try it out.

But the answer is: there is one instance of the Aggregator so they
will all get aggregated, no matter how many concurrent consumers you
have.


> --
> View this message in context: http://old.nabble.com/How-does-an-aggregato=
r-behave-with-multiple-consumers--tp26873948p26873948.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>


--=20
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus