WSO2 EI uses a thread pool executor to create threads and to handle incoming requests. This parameter controls the number of core threads used by the executor pool. If you increase this parameter value, the number of requests received that can be processed by EI increases, hence, the throughput also increases.
The nature of the integration scenario and the number of concurrent requests received by the ESB are the main factors that helps to determine worker_pool_size_core.
|This is the maximum number of threads in the worker thread pool. Specifying a maximum limit avoids performance degradation that can occur due to context switching. If the specified value is reached, you will see the error “SYSTEM ALERT - HttpServerWorker threads were in BLOCKED state during last minute”. This can occur due to an extraordinarily high number of requests sent at a time when all the threads in the pool are busy, and the maximum number of threads is already reached.||500|
|This is the maximum period of inactivity between two consecutive data packets, specified in milliseconds.||120000|
|This defines the keep-alive time for extra threads in the worker pool. The value specified here should be less than the socket timeout value. Once this time has elapsed for an extra thread, it will be destroyed. The purpose of this parameter is to optimize the usage of resources by avoiding wastage that results by having unutilized extra threads.||60|
|This defines the length of the queue that is used to hold runnable tasks to be executed by the worker pool. The thread pool starts queuing jobs when all the existing threads are busy, and the pool has reached the maximum number of threads. The value for this parameter should be -1 to use an unbound queue. If a bound queue is used and the queue gets filled to its capacity, any further attempts to submit jobs fail causing some messages to be dropped by Synapse.||-1|
|This defines the number of IO dispatcher threads used per reactor. The value specified should not exceed the number of cores in the server.||The default value is equal to number of cores in the server.|
|This is the value of the memory buffer allocated when reading data into the memory from the underlying socket/file channels. You should leave this property set to the default value.||16384|
|This defines the maximum number of connections allowed per host port.||32767|
|If this parameter is set to true, it is possible to open another socket on the same port as the socket that is currently used by the EI server to listen to connections. This is useful when recovering from a crash. In such instances, if the socket is not properly closed, a new socket can be opened to listen to connections.|
|This is used to configure the SessionInputBuffer size of http core. The SessionInputBuffer is used to fill data that is read from the OS socket. This parameter does not affect the OS socket buffer size.||8192|
|If this parameter is set to true, all services deployed to WSO2 EI cannot be accessed via the http|
|If this parameter is set to true, the user-agent HTTP header of messages passing through the ESB is preserved and printed in the outgoing message.|
This parameter allows you to specify the header field/s of messages passing through the EI that need to be preserved and printed in the outgoing message such as
|If this parameter is set to true, the HTTP connections with the back end service are closed soon after the request is served. It is recommended to set this property to false so that WSO2 EI does not have to create a new connection every time it sends a request to a back-end service. However, you may need to close connections after they are used if the back-end service does not provide sufficient support for keep-alive connections.|
|reverseProxyMode||This reverseProxyMode was introduced to avoid the Load Balance exposing for its own web service when REST call was initiated|