THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Camel 1.x does not have this feature implemented, the Seda queues in Camel 1.x will never wait.
| Note | ||
|---|---|---|
| ||
Using Request Reply over SEDA or VM only works with 2 endpoints. You cannot chain endpoints by sending to A -> B -> C etc. Only between A -> B. The reason is the implementation logic is fairly simple. To support 3+ endpoints makes the logic much more complex to handle ordering and notification between the waiting threads properly. This may change in the future if/when we implement such supporthas been improved in Camel 2.3 onwards, which allows you to chain as many endpoints as you like. |
Concurrent consumers
By default, the SEDA endpoint uses a single consumer thread, but you can configure it to use concurrent consumer threads. So instead of thread pools you can use:
...