...
Name | Since | Default | Description |
---|---|---|---|
|
|
| The maximum capacity of the SEDA queue (i.e., the number of messages it can hold). The default value in Camel 2.2 or older is |
|
|
| Number of concurrent threads processing exchanges. |
|
|
| Option to specify whether the caller should wait for the async task to complete or not before continuing. The following three options are supported: |
|
|
| Timeout (in milliseconds) before a SEDA producer will stop waiting for an asynchronous task to complete. See |
| 2.2 |
| Specifies whether multiple consumers are allowed. If enabled, you can use SEDA for Publish-Subscribe messaging. That is, you can send a message to the SEDA queue and have each consumer receive a copy of the message. When enabled, this option should be specified on every consumer endpoint. |
| 2.3 |
| Whether to limit the number of |
| 2.9 |
| Whether a thread that sends messages to a full SEDA queue will block until the queue's capacity is no longer exhausted. By default, an exception will be thrown stating that the queue is full. By enabling this option, the calling thread will instead block and wait until the message can be accepted. |
| 2.9 |
| Component only: The maximum default size (capacity of the number of messages it can hold) of the SEDA queue. This option is used if |
| 2.9.3 |
| Consumer only – The timeout used when polling. When a timeout occurs, the consumer can check whether it is allowed to continue running. Setting a lower value allows the consumer to react more quickly upon shutdown. |
| 2.11.1 |
| Whether to purge the task queue when stopping the consumer/route. This allows to stop faster, as any pending messages on the queue is discarded. |
| 2.12.0 | null | Define the queue instance which will be used by seda endpoint |
| 2.12.0 | null | Define the QueueFactory which could create the queue for the seda endpoint |
| 2.12.0 | false | Whether the producer should fail by throwing an exception, when sending to a SEDA queue with no active consumers. Only one of the options discardIfNoConsumers and failIfNoConsumers can be enabled at the same time. |
discardIfNoConsumers | 2.16 | false | Whether the producer should discard the message (do not add the message to the queue), when sending to a SEDA queue with no active consumers. Only one of the options discardIfNoConsumers and failIfNoConsumers can be enabled at the same time. |
Choosing BlockingQueue implementation
...
In the route below we use the SEDA queue to send the request to this async queue to be able to send a fire-and-forget message for further processing in another thread, and return a constant reply in this thread to the original caller.
Wiki Markup |
---|
{snippet:id=e1|lang=java|url=camel/trunk/camel-core/src/test/java/org/apache/camel/component/seda/SedaAsyncRouteTest.java} |
Wiki Markup |
---|
{snippet:id=e2|lang=java|url=camel/trunk/camel-core/src/test/java/org/apache/camel/component/seda/SedaAsyncRouteTest.java} |
mock
endpoint where we can do assertions in the unit test....
In this example we have defined two consumers and registered them as spring beans.
Wiki Markup |
---|
{snippet:id=e1|lang=xml|url=camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/spring/example/fooEventRoute.xml} |
As the beans are part of an unit test they simply send the message to a mock endpoint, but notice how we can use @Consume to consume from the seda queue.
Wiki Markup |
---|
{snippet:id=e1|lang=java|url=camel/trunk/components/camel-spring/src/test/java/org/apache/camel/spring/example/FooEventConsumer.java} |
Extracting queue information.
...