OK, thanks. So I think I get it now. Some params need defining on the
'from' side and some on the 'to' side. And the order the queue appears
in the routes is important. So this seems to work for me. Is this correct?
from('seda:insert?concurrentConsumers=2&size=3')
.delay(1000)
.log('seda ${body}')
from('direct:start')
.split(body())
.log('direct ${body}')
.to('seda:insert?blockWhenFull=true')
For instance, if the two routes are defined in the other order its
doesn't work as wanted.
Tim
On 12/09/2012 07:54, Claus Ibsen wrote:
On Wed, Sep 12, 2012 at 8:52 AM, Tim Dudgeon <tdudgeon...@gmail.com> wrote:
Great. That works. Thanks.
BTW, the example in the Camel in Action book (p 322) seems wrong then as it
describes it the way I originally had it.
The book is not wrong. The block parameter is on the *producer* side,
so you should have it in the "to".
Tim
On 12/09/2012 03:34, Willem jiang wrote:
You need set the seda endpoint parameter on the first one endpoint,
because Camel will pickup the created queue in the next endpoint.
Please change the first route like this
…
.log('direct ${body}')
.to('seda:insert?blockWhenFull=true&size=5')
