camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brad Johnson <brad.john...@mediadriver.com>
Subject Re: Disabling concurrency in camel route
Date Thu, 01 Sep 2016 19:57:33 GMT
True enough.  I used a resequencer to make sure they went in and out.
<unmarshal ref="recordn" />
<split>
<simple>${body}</simple>
<setHeader headerName="seqnum">
<simple>exchangeProperty.CamelSplitIndex</simple>
</setHeader>
<to uri="seda:processRecordsQueue" />
</split>

...

<resequence>
<stream-config capacity="50000" timeout="15000" />
<simple>in.header.seqnum</simple>
<to uri="seda:outQueue" />
</resequence>

On Thu, Sep 1, 2016 at 2:08 PM, Quinn Stevenson <quinn@pronoia-solutions.com
> wrote:

> I’d be careful with configuring the number of consumers on the SEDA queue
> if you need to preserve order - you’ll likely get stuff processed
> out-of-order.
>
>
> > On Sep 1, 2016, at 1:00 PM, Brad Johnson <brad.johnson@mediadriver.com>
> wrote:
> >
> > I'd second what Quinn said.  The other nice thing about the SEDA queue is
> > you can directly configure the number of threads that are consuming from
> it.
> >
> > On Thu, Sep 1, 2016 at 1:50 PM, Quinn Stevenson <
> quinn@pronoia-solutions.com
> >> wrote:
> >
> >> When I’ve hit situations like this, I’ve used the SEDA component to
> >> serialize the processing after the message was received.  All of the
> >> processing winds up in the SEDA route, and the actual receiving route
> (in
> >> this case, from Netty) just calls the SEDA route.  Something like
> >>
> >> <route id=“receiver”>
> >>    <from uri=“netty://…..>
> >>    <to “seda://do-work>
> >> </route>
> >>
> >> <route id=“serial-processor”>
> >>    <from uri=“seda://do-work <seda://do-work>>
> >>    <bean id=“processor” method=“process” />
> >>    <to uri=“destination://…” />
> >> </route>
> >>
> >>
> >>> On Aug 17, 2016, at 8:47 AM, Vitalii Tymchyshyn <vit@tym.im> wrote:
> >>>
> >>> You would need a combination.
> >>>
> >>> Ср, 17 серп. 2016 09:41 користувач robina <rashcroft@fomltd.com>
пише:
> >>>
> >>>> Thanks for the reply Vitalii,
> >>>>
> >>>> Would setting synchronous=true on its own ensure that only one message
> >> is
> >>>> processed by the route at any given time? Or is it the combination of
> >> the
> >>>> maxPoolSize of 1 and synchronous=true setting?
> >>>>
> >>>> Regards,
> >>>> Rob
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> View this message in context:
> >>>> http://camel.465427.n5.nabble.com/Disabling-concurrency-in-
> >> camel-route-tp5786531p5786533.html
> >>>> Sent from the Camel - Users mailing list archive at Nabble.com.
> >>>>
> >>
> >>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message