I have change a design like below
I already have multiple camel sub routes which perform different actions,
now my requirement was to align those sub routes in one flow for order
fulfillment.
1- For every new product i knew which sub routes suppose to be execute and
in which sequence, so i will
I agree the change I referenced in TransactionErrorHandler fixes the bug
you referenced (CAMEL-8424), but I believe that fix introduces another bug;
namely creating two transactions when only one should be created. It is
the presence of “PROPAGATION_REQUIRES_NEW” in my route example that makes
it
On Wed, Jan 3, 2018 at 4:35 PM, wrote:
> Oh. If so, should camel-netty4 sync=true be taken into consideration for the
> fix?
>
I would assume netty would allow existing worker tasks to complete.
However you are welcome to update your test case to test with sync=true
>
> Just wondering, mine i
thanks
On Thu, Jan 11, 2018 at 3:09 PM, Claus Ibsen wrote:
> Hi
>
> Yes its a little bug, its easier to reproduce if you make the
> processing slower, and speedup the file polling consumer to scan
> faster.
>
>
>
> On Tue, Jan 9, 2018 at 8:26 AM, Claus Ibsen wrote:
> > Hi
> >
> > Have patience,
Thanks for the clarification, Owain.
Imran, are your states the same across all of your nodes/systems? I agree
that orders always have a particular state, and they consequently have
rules for state transitions. Can you elaborate a little bit more on how
you can have a hundred different states fo
Hi
Yes its a little bug, its easier to reproduce if you make the
processing slower, and speedup the file polling consumer to scan
faster.
On Tue, Jan 9, 2018 at 8:26 AM, Claus Ibsen wrote:
> Hi
>
> Have patience, we will take a look at this later when we get time.
>
>
>
> On Tue, Jan 9, 2018 a
