The dm.execution.threads.max and dm.execution.threads.tasks settings are displayed in the onprem_direct.log, which is located at <dm-agent-dir>/logs/onprem_direct.log.
Here is an example:
INFO [CIExec-8] SID[] USER[] CC[] [] .crm.task.queue.EvenDistributionJobQueue - TID[QueryTask/XYZ] Running sequence XYZ:
RTC_4aa01f1d-d4a2-4b85-ad48-50b15516c1ca job QueryTask/XYZ request with id RTC_4aa01f1d-d4a2-4b85-ad48-50b15516c1ca (3 of max[10] with system threads occupied [20] of max[20])
In this example, the (3 of max[10] value reflects the setting for dm.execution.threads.tasks, which is the maximum number of system threads to execute single concurrent segment and task processes. (In this example, the maximum number is 10.)
The [20] of max[20]) value reflects the setting for dm.execution.threads.max. This setting is the maximum number of concurrent processes that are available across your entire system.
The message above means that you have three (out of a maximum of ten) concurrent processes inside one segment map or task and 20 system threads that are available to handle all types of tasks.
In SAS 360 Engage: Direct, you can change these settings in the cionprem.properties file that was created during the installation. For more information, see Dynamic Configuration of the Direct Agent.
onprem-direct.log Messages
You can encounter messages similar to the following in your onprem-direct.log, which is located at <dm-agent-dir>/logs/onprem_direct.log:
The application could not log on to the server "ci360-app-prod.xxx.xxx:8701". The load balancing object spawner timed out.
These messages can occur when requests are made to the SAS Object Spawner, but the SAS Object Spawner cannot start more SAS Pooled Workspace Servers because the number of SAS Pooled Workspace Servers is too low.
To increase the number for dm.execution.threads.max, you need to check the following settings from SAS® Management Console:
SAS Pooled Workspace Server Settings
Navigate to SAS Management Console ► Server Manager ► SASApp ► SASApp – Logical Pooled Workspace Server ► right-click SASApp –Pooled Workspace Server ► Properties ► Options ► Advanced options ► the Load Balancing tab.
Launch timeout:
Recycle activation limit:
Server process maximum: (is the number of available Workspace server sessions)
Server process minimum:
Inactive process shutdown timeout:
Depending on the value for Server process maximum (see above), you need to increase dm.execution.threads.max, which is available in the cionprem.properties file.
For more information about these settings, see Tune the Direct Agent.
Note:
- After you adjust the settings for the SAS Pooled Workspace Server, you must restart the SAS Object Spawner.
- Changing the settings in the cionprem.properties file does not require you to restart the Direct Agent.
- dm.execution.threads.max should be lower than the setting for the SAS Pooled Workspace Server ► Server process maximum. (As a recommendation, the SAS Pooled Workspace Server ► Server process maximum setting should be double the dm.execution.threads.max setting.)