Types of Restarts

There are three types of restarting services:

Restart during Critical Memory Limit:

Whenever the memory limit of a process (instance of Windows service) reaches a Critical Value, the service is immediately restarted. During the Critical memory value of the process, there are high chances of the process throwing OutOfMemoryException. By restarting the process, we the OutOfMemoryException exception, and thereby, the workflows pending in the queue are avoided.

For more information about Critical Memory Limit, see Process Memory Calculation.

Restart during Warning Memory Limit:

When the memory limit of a process reaches a critical limit, the service is restarted immediately. Even when the service is in high load usage, the restart is unavoidable. To avoid restarting during high load usage, we need to restrict the process from reaching the critical memory limit.

The Client service will monitor this process. Whenever the service finds that the process has reached the warning memory limit for a particular duration of time, it will make a note of it.

If the warning memory limit is exceeding at a low usage time (night times), the service is restarted immediately at that time. The low usage time is configurable in the Configuration Settings.

This attribute is not enabled by default. The Administrator will have to enable in the Configuration Settings.

Restart during Maintenance Phase:

Load of the Workflow tasks will be maximum during a particular phase (duration) in a business cycle. For example, payroll clearance will happen at the end of every month.

In such situations, it is better to restart the service in advance to clean all unknown objects which may still be consuming the memory, so that there is sufficient memory to load the workflows for execution. Restart can happen at a low usage time such as late nights. The low usage time is configurable in the Configuration Settings.

This attribute is not enabled by default. The Administrator will have to enable in the Configuration Settings.