Threads — Specifies that all steps after this node are processed asynchronously
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.
Table 103 describes the properties you can specify using the properties editor.
Table 103. Threads Properties
Name | Description |
---|---|
Time Unit | Specifies the unit of measure for timeout values. |
Inherit Error Handler | Specifies whether the node should use the error handler configured for the route.
The default is Disabled . |
Pool Size | Specifies the core pool size for the thread pool. |
Max Pool Size | Specifies the maximum pool size for the thread pool. |
Max Queue Size | Specifies the maximum size of the thread queue. |
Thread Name | Specifies an expression, in the simple language, that is used to generate unique names for the threads used to process messages. |
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. |
Caller Runs When Rejected | Specifies whether tasks rejected by the thread pool are executed by the calling
thread. The default is Disabled . |
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 Camel XML file. |
Description | Specifies a text description for the node. This description is included in the generated XML file, but it is informational only. It is not used by Apache Camel. |