How can I limit the number of event rule subroutines running?

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• EFT v8.x
• See also:
• https://kb.globalscape.com/Knowledgebase/11620/Using-Advanced-Properties-to-optimize-running-asynchronous-events
• https://kb.globalscape.com/Knowledgebase/10581/Advanced-Workflows-affect-system-performance

QUESTION

How can I limit the number of event rule subroutines running?

ANSWER

The number of event rule subroutines running can be limited by setting the following advanced properties in the AdvancedProperties.json file. (Search in the EFT admin interface for the advanced properties topic: click Help > Help Contents.)

• Asynchronous subroutine global number of threads running

To specify the maximum number of simultaneous asynchronous event rule subroutines running (per server), add:

RunningAsyncSubroutinesLimit

The default is "10"; "0" = no limit

• Asynchronous subroutine queue size per-site

To specify the maximum number of asynchronous event rule subroutines that may be queued (per site) before dropping new subroutine, add:

QueuedAsyncSubroutinesLimit

The default is "0", which means no limit; enter a non-zero value to limit it.

To force subroutine to wait until an AWE task completes, make sure that:

• Subroutines are called asynchronously (i.e., the caller rule HAS NO IF FAILED section when calling subroutine)
• AWE tasks are called synchronously (i.e., subroutine has IF FAILED section when calling workflow.) This will force subroutine to wait until AWE task completes.