The issue is not a-synchronic interaction between the SEDA producer and the SEDA consumer, that is fine, I know it is an asynchronous interaction, but the fact that the steps within the SEDA route are not executed in a synchronous manner. i.e. setting the synchronous=true property in the SEDA consumer is not causing the desired effect.
Best regards, Alex soto > On Feb 6, 2020, at 12:09 PM, WEIQUAN YUAN <weiquan.y...@gmail.com> wrote: > > as it is known that SEDA component is asyn component, but direct is sync > one, can you use direct instead of seda? > > On Wed, Jan 29, 2020 at 2:42 PM Alex Soto <alex.s...@envieta.com> wrote: > >> Thanks Claus, >> >> I tested adding synchronous=true to the SEDA consumer, but it does not >> make any difference. >> The only thing that worked was to add asyncDelayed=“false” to the delay >> EIP. >> Is this perhaps a bug? >> >> >> Best regards, >> Alex soto >> >> >> >> >>> On Jan 29, 2020, at 1:48 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: >>> >>> On the consumer, eg the from >>> >>> On Wed, Jan 29, 2020 at 5:41 PM Alex Soto <alex.s...@envieta.com> wrote: >>>> >>>> Thanks Claus…. >>>> >>>> Oh, I see, after returning from the delay, it is a different thread >> that processes the rest of the route. >>>> Where should the synchronous=true be added, in the Producer or >> Consumer or both URIs? >>>> >>>> Best regards, >>>> Alex soto >>>> >>>> >>>> >>>> >>>>> On Jan 29, 2020, at 11:13 AM, Claus Ibsen <claus.ib...@gmail.com> >> wrote: >>>>> >>>>> The delay makes it asynchronous, set synchronous=true on the seda >> endpoint >>>>> >>>>> On Wed, Jan 29, 2020 at 4:52 PM Alex Soto <alex.s...@envieta.com> >> wrote: >>>>>> >>>>>> Hello, >>>>>> >>>>>> I have a question about SEDA consumer and parallelism. When I set >> the concurrentConsumers=1 and send multiple messages in parallel, I expect >> to see the messages being processed in sequence, but what I see in the logs >> is that they are being processed in parallel. >>>>>> >>>>>> My route looks more or less like this: >>>>>> >>>>>> <route id=“myroute"> >>>>>> <from >> uri=“seda:myconsumer?purgeWhenStopping=true&concurrentConsumers=1&exchangePattern=inOnly”/> >>>>>> <delay> >>>>>> <constant>1000</constant> >>>>>> </delay> >>>>>> </route> >>>>>> >>>>>> From logs, I can see messages being processed in parallel by this >> route. Any idea? >>>>>> >>>>>> (Camel version is 3.0.1) >>>>>> >>>>>> Best regards, >>>>>> Alex soto >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Claus Ibsen >>>>> ----------------- >>>>> http://davsclaus.com @davsclaus >>>>> Camel in Action 2: https://www.manning.com/ibsen2 >>>> >>> >>> >>> -- >>> Claus Ibsen >>> ----------------- >>> http://davsclaus.com @davsclaus >>> Camel in Action 2: https://www.manning.com/ibsen2 >> >> > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Weiquan Yuan > Located in Ottawa, Canada
