Return-Path: 
 <users-return-19961-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 D8DEF38CD
	for <apmail-camel-users-archive@www.apache.org>;
 Wed,  4 May 2011 11:15:31 +0000 (UTC)
Received: (qmail 2469 invoked by uid 500); 4 May 2011 11:15:31 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 2436 invoked by uid 500); 4 May 2011 11:15:31 -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 2428 invoked by uid 99); 4 May 2011 11:15:31 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 May 2011 11:15:31 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [80.237.132.225] (HELO wp218.webpack.hosteurope.de)
 (80.237.132.225)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 May 2011 11:15:22 +0000
Received: from p5de94010.dip0.t-ipconnect.de ([93.233.64.16]
 helo=[172.17.16.53]); authenticated
	by wp218.webpack.hosteurope.de running ExIM with esmtpsa
 (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	id 1QHa2o-0004St-C4; Wed, 04 May 2011 13:15:02 +0200
Message-ID: <4DC13535.1080905@catify.com>
Date: Wed, 04 May 2011 13:15:01 +0200
From: Claus Straube <claus.straube@catify.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Re: Another problem?
References: <BANLkTimvoqKKaxmeDwd-NDxZr2fqBScyJQ@mail.gmail.com>
In-Reply-To: <BANLkTimvoqKKaxmeDwd-NDxZr2fqBScyJQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-bounce-key: 
 webpack.hosteurope.de;claus.straube@catify.com;1304507722;00c2c9a0;
X-Virus-Checked: Checked by ClamAV on apache.org

Hi Ichsan,

if you turn on tracing (<camelContext trace=true>) you can see the 
threads. What do you mean by "concurrently"? If I see this correct, 
you're refering to a Spring bean. This is per default a singleton. So 
you should have only one instance of mocky...

Best regards - Claus

On 04.05.2011 13:02, Muhammad Ichsan wrote:
> Dear All
>
> I found another problem in Camel. Given context file (the java bean
> code is self-explainable):
>
> <route>
> 			<from uri="direct:casemx" />
>
> 			<setExchangePattern pattern="InOut" />
> 			<to uri="activemq:preparation" />
>
> 			<to uri="bean:mocky?method=delay2000" />
>
> 			<to uri="mock:result" />
> 		</route>
> 		
> 		<route>
> 			<from uri="activemq:preparation" />
> 			<to uri="bean:mocky?method=delay1000" />
> 			<to uri="log:ho" />
> 		</route>
>
>
> With activemq concurrency 10. If I send 8 message at once into
> direct:casemx, delay1000 method will be called concurrently. But...
> delay2000 is not!!! Do I miss something here? Or this is just another
> bug???
>