Hi,
SEDA is asynchronous, and the messages are exchanged on a BlockingQueue.
To avoid overhead, you can use the size attribute to limit the number of
messages to handle:
from("seda:workpipie?concurrentConsumers=25&size=1000")
Regards
JB
On 06/15/2011 02:54 PM, Frederic Tuttle wrote:
I have been using seda queues to multithread some processing such as:
from("seda:workpipe?concurrentConsumers=25").process(new
WorkProcessor());
If I leave the queue unbounded, I will run out of heap space if my load is
too high and my threads are too few.
If I limit the queue size, the queue fills up and message delivery fails.
Should I expect some sort of flow control because seda is implemented as a
blocking queue ? or is there total decoupling from the provider ?
What are ways of dealing with this issue other than tweaking the settings ?
Thanks for your help.
-FT
