THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Name | Default | Description |
|---|---|---|
size | 1000 | The maximum size of the SEDA queue |
concurrentConsumers | 1 | Camel 1.6.1/2.0: Number of concurrent threads processing exchanges. |
waitForTaskToComplete | Camel 2.0: Option to specify if the caller should wait for the async task to be complete or not before continuing. The following 3 options is supported: Always, Newer or IfReplyExpected. The first two options is self explained. The last will only wait if the message is Request Reply based. The default option is IfReplyExpected. See more information about Async messaging. |
Changes in Camel 2.0
In Camel 2.0 the Seda component supports using Request Reply where the caller will wait for the Async route to complete. For instance:
| Code Block |
|---|
from("mina:tcp://0.0.0.0:9876?textline=true&sync=true").to("seda:input");
from("seda:input").to("bean:processInput").to("bean:createResponse");
|
In the route above we have a TCP listener on port 9876 that accepts incoming requests. The request is routed to the seda:input queue. As its a Request Reply message we will wait for the response. So when the consumer on the seda:input queue is complete it will copy this response to the original message as response.
Camel 1.x does not have this feature implemented, the Seda queues in Camel 1.x will newer wait.
Concurrent consumers
By default Camel uses a single consumer. You can configure the endpoint to use concurrent consumers. So instead of thread pools you can use:
...
| Include Page | ||||
|---|---|---|---|---|
|