camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Straube <claus.stra...@catify.com>
Subject Re: Another problem?
Date Wed, 04 May 2011 11:15:01 GMT
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???
>



Mime
View raw message