camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <willem.ji...@gmail.com>
Subject Re: Parallel processing route
Date Mon, 17 Mar 2008 09:40:21 GMT
Hi aswin,

I just filled a JIRA[1] and committed the patch for it.
Please check it out.

[1]https://issues.apache.org/activemq/browse/CAMEL-389

Cheers,

Willem
aswin.nair wrote:
> willem.jiang wrote:
>   
>> Yes ,the  multicast  do not as you want.
>> Here is the MulticastProcessor's process code.
>>
>>     
> Yes, I had figured that out. I tried different combinations of route to get
> this to work without any luck. Chirnio's suggestion to use the following
> also did not work.
>
>
> from("cxf:bean:soapMessageEndpoint").process(myProc).thread(5).to("direct:a");
>  from("direct:a").aggregator(header("txid"),
> aggregationStratergy).to("bean:testBean?methodName=processSOAP") ; 
>
> The aggregator's cosumer is EventDrivenPollingConsumer and causes the route
> to return immediately, as it just transfers the message to the queue which
> aggregator is listening to. So basically not much of use in CXF two way MEP
> case. 
>
>
> willem.jiang wrote:
>   
>> Maybe we could define a new ParallelizedMulticastProcessor  for calling 
>> the to endpoint in different thread, and a barrier class could help us 
>> to get the calling threads aggregated.
>>
>>     
>
> I was thinking on the same lines. But wanted to make sure that I was not
> missing anything already present that I was not aware of. May be I should
> get working on this, I think this would also need new DSL methods or
> probably an argument to multicast() to indicate that Parallelism is
> intended. 
>
>
>
> willem.jiang wrote:
>   
>> BTW, you can find ThreadProcessor for Thread syntax implementation.
>>
>>     
>
> Went through this also many times. We could make MultiCast, if set in
> parallel processing mode, invoke the processors asynchronously (using 
> process(Exchange, callback))  and blocking until  all the callbacks from all
> the parallel routes are received. This would be a pretty simple change I
> guess. 
>
> What do you think of this approach? 
> Aswin
>
>
>   


Mime
View raw message