|Parameter Name||Description||Default Value|
|worker_pool_size_core||Initial number of threads in the worker pool. If the number of live threads is less than the value defined here, a new thread is created to process the response. Nature The nature of the integration scenario and the number of concurrent requests received by the ESB are the main factors that helps help to determine worker_pool_size_core.|
Maximum number of threads in the worker pool.
If the queue (
Maximum period of inactivity between two consecutive data packets. Given in milliseconds.
The keep-alive time in seconds for idle threads in the worker pool. Once this time has elapsed for an idle thread, it will be destroyed.
The purpose of this parameter is to optimize the usage of resources by avoiding wastage that results from having idle threads.
The length of the queue that is used to hold runnable tasks to be executed by the worker pool.
If the number of live threads is equal to the core pool size (
If the queue is full, all threads are busy and the number of live threads is equal to the max pool size (
|io_threads_per_reactor||Defines the number of IO dispatcher threads used per reactor. The value for this property should not exceed the number of cores in the server.|
|io_buffer_size||Size in bytes of the buffer through which data passes.|
|http.max.connection.per.host.port||Defines the maximum number of connections allowed per host port.|
|http.socket.reuseaddr||If this parameter is set to |
This is used to configure the