Thread creation is relatively expensive in terms of compute cycles and therefore can account for increased delays in responding to client requests. So in order to minimize the delay associated with the thread creation a 'thread pool' is created and managed in Artix, and in almost all modern application server architectures.

Thread pool settings are available to tune the size and scalability of the thread pool based on your application requirements. The initial_threads setting is the number of threads that will be available to your application once the initialization of Artix is complete. Similarly, the low_water_mark is the minimum number of threads that you want to be available in the thread pool. And likewise the high_water_mark is the maximum number of threads you want in the pool, at which point incoming requests are queued up to the max_queue_size until a worker thread becomes available to execute the request.

This article talks more about configuration of these properties for JAX-RPC applications:

community.microfocus.com/.../22709.how-to-configure-thread-pools-in-artix-jax-rpcc.aspx

Cheers and best regards,

-Scott Kay

Fro further details please also see

- the "Artix 5.6.3 Configuration Reference, C Runtime", chapter "Multi-threading"

- the "Artix 5.6.3 Configuring and Deploying Artix Solutions, C Runtime", chapter "Artix Configuration"

The above documents are available below:

   supportline.microfocus.com/productdoc.aspx

by selecting

   Product family: CORBA Middleware

   Product: Artix

   Release: 5.6.3

and scroll down to the "Artix 5.6.3 C " collection of documents.