CREATING: DispatcherMgr
This entry is logged when the SPO Dispatcher Manager is created. This is the first step in initializing the SPO. When you see this entry, the SPO process has just started. Any preceding entries in the SPO log were from a previous instance of the SPO.
This event appears in the log with the following format:
Timestamp CREATING: DispatcherMgr
MaxDispatchers: MaxDispatchers
MaxTotalSlaves: MaxTotalSlaves
ShutdownGracePeriod: GracePeriod
RunAuthorizedAppsOnly: AuthAppsOnly
Timestamp
Identifies the event timestamp. It has the following format:
yyyy/mo/dd_hh:mi:ss.fff
yyyy
Identifies a four-digit year value
mo
Identifies a two-digit month value
dd
Identifies a two-digit day value
hh
Identifies a two-digit military hour value
mi
Identifies a two-digit minute value
ss
Identifies a two-digit second value
fff
Identifies a three-digit millisecond value
MaxDispatchers
Identifies the maximum number of dispatchers that can be active in the SPO
Limits: 1000 maximum
Default: 48
MaxTotalSlaves
Identifies the maximum number of slaves that can be active in the SPO.
When a dispatcher is created, it attempts to reserve the maximum number of slaves that it has been configured to use even if it will only initially start one. This means that if each dispatcher is configured to manage four slaves, then only 12 dispatchers can be created. Each dispatcher will reserve four slaves when it is created. The thirteenth dispatcher created will have no slave quota left in the SPO.
Limits: There is no limit on this value. This value may be limited by resources available in the operating system. The recommended maximum is 99.
Default: 48
GracePeriod
Identifies the period in milliseconds (ms) that the SPO will delay a shutdown request starting the SPO shutdown sequence. This is designed to give the ASOs a chance to complete any outstanding Call4GL/JsonRpcRequest requests.
Default: 15 seconds
AuthAppsOnly
Indicates whether the OpenROAD ImageFile component of the application signature must be registered with ASOLib. (An image file can be registered with ASOLib but does not have to use ASOLib.) Valid values include:
TRUE
Specifies that the OpenROAD ImageFile must be registered with ASOLib for it to be used by the SPO in an ASO Initiate request.
FALSE
Specifies that the OpenROAD ImageFile does not have to be registered to be used by the SPO in an ASO Initiate request.
Default: TRUE
Note: We strongly recommend that you set this value to TRUE. This helps ensure that a rogue client cannot substitute an unauthorized ImageFile and request that the SPO use it in the ASO Initiate request.
Last modified date: 12/20/2023