THE INFORMATION IN THIS ARTICLE APPLIES TO:
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
Type: uint32_t
Default Value: 10
Minimum Value: 0
Maximum Value: 4294967295
Description: The maximum number of simultaneous asynchronous event rule subroutines running. A value of 0 indicates there is 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
Type: uint32_t
Default Value: 0
Minimum Value: 0
Maximum Value: 4294967295
Description: The maximum number of asynchronous event rule subroutines that may be queued before dropping new subroutine. A value of 0 (default) indicates there is no limit.
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.