Return-Path: 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 197B7F0D8 for ; Wed, 17 Apr 2013 06:08:36 +0000 (UTC) Received: (qmail 45206 invoked by uid 500); 17 Apr 2013 06:08:35 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 44757 invoked by uid 500); 17 Apr 2013 06:08:30 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 44707 invoked by uid 99); 17 Apr 2013 06:08:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Apr 2013 06:08:28 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=URI_HEX X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Apr 2013 06:08:23 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1USLWv-0007ye-6g for users@camel.apache.org; Tue, 16 Apr 2013 23:07:41 -0700 Date: Tue, 16 Apr 2013 23:07:41 -0700 (PDT) From: Gnanaguru S To: users@camel.apache.org Message-ID: <1366178861182-5730994.post@n5.nabble.com> Subject: Camel aggregation logic fails in case of two camel nodes MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, I have a use case where I have used splitter and aggregation patterns. The diagram below shows the message flow. I have a message with ten trades: it reaches the splitter -> gets split into ten messages -> each message gets enriched -> after enrichment, the messages are aggregated into single message and sent to the output queue. Figure 1: Use case description I am using the bread-crumb id as the correlation id for the messages. It works perfectly fine for a single camel instance. When I test the same scenario with two or more camel instances simultaneously at a time, this aggregation logic doesn't work because the messages are consumed by many camel node. Logically I am not able to aggregate. Hope its understandable. What is the advice for me ? If I want to do a aggregation in a distributed or clustered scenario ? Is there any pattern which can solve this problem ? Please help. Regards Guru @gnanagurus -- View this message in context: http://camel.465427.n5.nabble.com/Camel-aggregation-logic-fails-in-case-of-two-camel-nodes-tp5730994.html Sent from the Camel - Users mailing list archive at Nabble.com.