Orbix Question:

The variables in the thread_pool namespace specify policies that configure multi-threading. This namespace includes the following variables:

high_water_mark

high_water_mark specifies the maximum number of threads allowed in the thread pool. Defaults to -1, which means that there is no limit on the maximum number of threads.

initial_threads

initial_threads specifies the number of initial threads in the thread pool.

Defaults to the low_water_mark thread limit (or 5, if the low_water_mark is not set).

low_water_mark

low_water_mark specifies the minimum number of threads in the thread pool. If this variable is set, the ORB will terminate unused threads until only this number exists. The ORB can then create more threads, if needed, to handle the items in its work queue. Defaults to -1,which means do not terminate unused threads.

max

max sets the maximum number of threads that are available for JMS message processing.

max_queue_size

max_queue_size specifies the maximum number of request items that can be queued on the ORB's internal work queue. If this limit is exceeded, Orbix considers the server to be overloaded, and gracefully closes down connections to reduce the load. The ORB will reject subsequent requests until there is free space in the work queue. Defaults to -1, which means that there is no upper limit on the size of the request queue. In this case, the maximum work queue size is limited by how much memory is available to the process.

stack_size

stack_size sets the ORB's internal threads stack size. This is only available in the C++ ORB; the Java API does not allow manipulation of the thread stack size.