Name
Threads — Specifies that all steps after this node are processed asynchronously
Usage
The threads pattern specifies that the nodes after it in the route are processed asynchronously. This means that the route can use multiple threads to process messages and that the client will not wait for a reply.
The threads pattern can be used anywhere in the body of a route.
Properties
Table 6.5 describes the properties you can specify using the properties editor.
Table 6.5. Threads Properties
| Name | Description |
|---|---|
| Time Unit | Specifies the unit of measure for timeout values. |
| Pool Size | Specifies the core pool size for the thread pool. |
| Max Pool Size | Specifies the maximum pool size for the thread pool. |
| Thread Name | Specifies an expression, in the simple language, that is used to generate unique names for the threads used to process messages. |
| Max Queue Size | Specifies the maximum size of the thread queue. |
| Executor Service Ref | Specifies a reference for looking up the
executorService to use for
thread pool management. |
| Keep Alive Time | Specifies the amount of time a thread can be idle before it is reaped. |
| Inherit Error Handler | Specifies if the node should use the error handler configured for the route. |
| Caller Runs When Rejected | Specifies that tasks rejected by the thread pool are executed by the calling thread. |
| Rejected Policy |
Specifies how tasks rejected by the thread pool are handled. Valid values are:
|
| Id | Specifies a unique identifier for the endpoint. The Id can be used to refer to the endpoint in the Apache Camel configuration file. |
| Description | Specifies a text description of the bean. The description is included in the generated XML file. |
 |  |  |
 |
