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.
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
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
On Wed, Sep 12, 2012 at 9:31 AM, Tim Dudgeon tdudgeon...@gmail.com wrote:
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?
I'm trying to use the SEDA component with the concurrentConsumers options.
I'm setting a queue size and expecting the calling thread to block, but
its not working for me.
I have groovy code like this:
def vals = 1..10
println vals
CamelContext camelContext = new DefaultCamelContext()
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=truesize=5')
--
Willem Jiang
FuseSource
Web:
