Skip to content
pCon.configurator onlineDocumentation
Esc
↑↓navigate↵open⌘Jpreview
On this page

HTTP Request Executer

The initialization of the HTTP request executor can now be configured through the following application properties:

Synopsis

egr.eai.server.http.thread_pool.max_pool_size

The maximum number of threads in the pool. The value must be within -1 and 1024 (both inclusive). The default value is -1.

If the value is -1, the actual maximum pool size is equal to the number of processor available to the Java runtime at startup, multiplied by two. Note that in case of Intel Hyper-Threading, this is the number of visible CPUs, not the number of CPU cores (i.e., in the most common case, 8 instead of 4).

If the value is zero, no thread pool is used. Instead, all requests are serviced by the HTTP server thread. This may be useful for special cases where it is known that the server services requests for a single single-threaded client.

Synopsis

egr.eai.server.http.thread_pool.keep_alive

The number of seconds to keep an idle thread alive. The value must be withn -1 and 2^31-1 (both inclusive). The default value is 5.

If the value is -1, threads are kept alive infinitely. In general, a value of zero should be avoided as it would result in continual thread replacement.

This property is ignored if no thread pool is used (i.e. if the maximum pool size is zero).

Synopsis

egr.eai.server.http.thread_pool.queue_size

The upper bound on the size of the queue used to store pending requests. The value must be within -1 and 65536 (both inclusive). The default value is 1024.

A value if -1 results in a queue with unlimited length. Otherwise, when the HTTP server adds a request to the queue, and the queue size has reached its upper bound, the HTTP server waits until a request has been removed from the queue by one of the threads servicing requests.

The special value zero is allowed and results in the use of a queue where each add operation of the HTTP server waits for a corresponding remove operation of one of the request service threads.

This property is ignored if no thread pool is used (i.e. if the maximum pool size is zero).