Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Work Tasks

Default Settings

  • Last UpdatedJun 06, 2024
  • 2 minute read

Configuration has the default setting section "DefaultConfig". Default setting is for MonitorService property, CriticalMemory and WarningMemory sections. If these settings are not mentioned for a service, then the values are taken from the default settings. If a service has its own settings, then those settings will override the default settings.

If the "MonitorService" attribute is not present or its value is empty for a specific service, then the default section value is taken.

If the "MonitorService" attribute is not present even in the default section, then the MonitorService="true" will be considered.

If "MonitorService"="false" for a specific service, then that service will not be monitored. But, the same service can be restarted as it may be a dependent service of other AVEVA Work Tasks Window service. If service monitoring has restarted a AVEVA Work Tasks Window service, then its dependent services are restarted.

If the CriticalMemory node is not present or if the MemoryLimitInMB attribute is empty for a specific service, then the default setting is considered. If the MemoryLimitInMB value is zero, then the critical memory limit will not be monitored.

CriticalMemory monitoring is enabled by default. The critical memory limit is monitored even if "CriticalMemory" is not present in the default section. The monitoring is done based on the "PrivateMemorySize64" property of a process.

By default, the value for "MemoryLimitInMB" is considered as 1500MB for a 64 bit machine.

Similarly, for the WarningMemory section too, if the node value of "WarningMemory" is not found or if any of its attribute value is empty for a service, then the default configuration settings will be considered for a service.

If the value of MemoryLimitInMB attribute is zero, then the WarningMemory will not be monitored. If the WarningMemory section is not found in the defaultConfig section, then the WarningMemory monitoring will be disabled for all services which depend on the default configuration.

The Advanced Service, WorkFlow Engine, Task Scheduler, and Communication Service sections do not have any settings by default. These sections will take the values from the default settings. If you want to change any specific value, then you can mention the values in the respective sections.

TitleResults for “How to create a CRG?”Also Available in