If an OutOfmemoryException is triggered in regular intervals , it is usually a natural phenomenon . During a running time of 10m approximately 450 processes are processed. Since a maximum of 1.6 GB of memory is available to a process, a memory overflow can occur.
====== Troubleshooting: ====== Regular OutOfMemoryException 1) ====== Solution: ====== The solution is to replace the simple delegate with a QueuedDelegate . This is able to restore orders to a temporary queue. The jobs are not restarted until the queue can process new jobs. ^ QueuedDelegate ^ Properties and their meaning | | QueueName | Load balancing is performed only within the same named queue. Here, the system can be divided into different queue areas. Otherwise leave default: DefaultQueue | | MaxQueueEntries | How many processes max. If you are in the same queue with 2 different delegates in the same queue, but have different Max entries, the behavior may be somewhat difficult to comprehend, since then the respective queue is valid for the respective queue Delegate another limit of the max. Utilization before something is actually gequeued. If in doubt, adjust to the same value, then the behavior becomes more transparent. | | QueueWaitTimeout | Since all processes are actually running (only on pause) during this procedure, this value indicates how many minutes the queue should wait. Default = 30 (minutes). After this time, the wait is terminated and a task is generated. In such a case, the remaining processes have to be pushed manually |