I just commit a quick fix in master branch[1], as it’s a new feature for camel,
I don’t have plan to merge it to other branches. You can merge it back to other
camel branch if you like.
[1]https://issues.apache.org/jira/browse/CAMEL-7491
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.c
Yes, Current Camel throttler implementation is based on the
DelayProcessorSupport, you need to extend the throttler to override the Delay
behaviour.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitte
Hi
Yeah you can get such situations in the Java DSL. Java Generics is not
up for the task of a full fledged DSL.
In Camel 3.0 we should improve the throttle DSL to not require child
nodes and hence the Java DSL ought to work.
You can split the route into other routes and link using direct to
wor
Hi
I have created ticket
https://issues.apache.org/activemq/browse/CAMEL-2630
You can comment any ideas you may have to improve the mock to better
support your use case
On Sat, Apr 10, 2010 at 8:35 PM, Pavel wrote:
> Hi,
>
> I'm fine with +/- 10%, but perhaps with my massive examples I shifted
Hi
You could just let it route to the mock endpoint.
And then afterwards check at what time they arrived at the mock
endpoint, to see if there is at most 7 within a second.
And btw I think we should add a header to the mock endpoint which
records the arrival time. For now you have to do that your
Hi,
I'm fine with +/- 10%, but perhaps with my massive examples I shifted the
focus away from the original issue:
Route throttler is configured for 7 messages per second, but mock endpoint
will match message count of 7, or 14, or anything in between.
Thus the closest test I can do to verify inten
Hi
You can newer trust 100% on System time millis as its not accurate. So
make assertions on a given +/- delta.
On Sat, Apr 10, 2010 at 5:27 PM, Pavel wrote:
> Tried that, and noticed a few differences. maximumRequestsPerPeriod is 7.
>
> * Expected message count <7 consistently fails with "Exp
Tried that, and noticed a few differences. maximumRequestsPerPeriod is 7.
* Expected message count <7 consistently fails with "Expected , but was
<7>"
* Expected message count 7-11 passes
* Expected message count 12,13 seems racy: sometimes test would fail with
"Expected , but was "
* Expected mes
Hi
Can you try with
targetMock.assertIsSatisfied(1000);
On Sat, Apr 10, 2010 at 11:43 AM, Pavel wrote:
> Hello,
>
> I'm facing strange behaviour of throttler + mock endpoint when route under
> test is this:
>
>
>
>
>
>
>
>
>
> test itself defines producer
