How to configure thread pool settings in Orbix 6.3

Dominique Sacre · 2013-06-10T09:38:00+00:00

Summary This article clarifies the thread pool settings in Orbix 6.3 Environment Orbix 6.3All Supported Operating Systems Question/Problem Description How to configure the thread pool settings in Orbix 6.3 Clarifying Information Orbix provides excellent support for multi-threaded applications. Orbix libraries are multi-threaded and thread-safe. Orbix servers use standard POA policies to enable multi-threading. The ORB creates a thread pool that automatically grows or shrinks depending on demand load. Thread pool size, growth and request queuing can be controlled by configuration settings without any coding. Error Message Defect/Enhancement Number Cause Resolution The variables in the thread_pool namespace specify policies that configure multi-threading. This namespace includes the following variables: high_water_markhigh_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_threadsinitial_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_marklow_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. maxmax sets the maximum number of threads that are available for JMS message processing. max_queue_sizemax_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_sizestack_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. Workaround Notes For further details on multi-threading in Orbix 6.3 please consult the Orbix 6 "Configuration Reference" and the Orbix 6 "CORBA Programmer's Guide" available at: https://www.microfocus.com/documentation/orbix/ Attachment #Orbix#KnowledgeDocs

Summary	This article clarifies the thread pool settings in Orbix 6.3
Environment	Orbix 6.3 All Supported Operating Systems
Question/Problem Description	How to configure the thread pool settings in Orbix 6.3
Clarifying Information	Orbix provides excellent support for multi-threaded applications. Orbix libraries are multi-threaded and thread-safe. Orbix servers use standard POA policies to enable multi-threading. The ORB creates a thread pool that automatically grows or shrinks depending on demand load. Thread pool size, growth and request queuing can be controlled by configuration settings without any coding.
Error Message
Defect/Enhancement Number
Cause
Resolution	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.
Workaround
Notes	For further details on multi-threading in Orbix 6.3 please consult the Orbix 6 "Configuration Reference" and the Orbix 6 "CORBA Programmer's Guide" available at: https://www.microfocus.com/documentation/orbix/
Attachment

#Orbix
#KnowledgeDocs

Sign up

Please log in or register:

Welcome to the Rocket Forum!

Please log in or register:

Scanning file for viruses.

This file cannot be downloaded