Thanks Roman for the JIRA link.
My question initially came from experimenting with trying to provide
multiple threads around the http component to increase throughput. I admit
I'm having some general confusion trying to get the thread processor to
behave "the way I think it should". Since I was at
2009/2/3 huntc :
>
> I think that what you're looking for is something akin to the
> "concurrentConsumers" parameter for a JMS endpoint.
> My recommendation is to raise a JIRA request for an enhancement so that the
> SEDA endpoint can receive a concurrentConsumers parameter. After all seems
> to m
SEDA is a poor-mans JMS endpoint.
Anyone agree/disagree?
--
View this message in context:
http://www.nabble.com/understanding-SEDA-and-Thread-processor-tp21612576s22882p21817985.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hello all,
I'm looking for some advice regarding SEDA and threads (camel 1.5.0). I'd
like to be able to use multiple threads to pull from a SEDA component.
I've read the SEDA docs[1] including the section about Thread Pools[2], but
I'm not quite able to get the behavior I want/expect.
I've start
