The disasterbrakes property of Galaxy Core Service must be set to true so that you can configure the memory threshold.
To set the property to true, in SAP NetWeaver Administrator navigate to , open the Services tab and select the Galaxy Core Service.
It is possible that some business process models have errors and can therefore cause server crashes due to out-of-memory problems. The reasons for this can be endless loops, endless recursive invocations of subprocesses, or the creation of large numbers of tokens for parallel splits. Restarting the engine will not help you to get the BPM engine running again. To prevent the BPM system from such disaster situations, configure the threshold values for the number of process instances and tokens that the system can create. You can perform the configuration either for the entire BPM system or for specific process definitions.
The memory threshold mechanism works completely separately on every server node in the cluster. Configured threshold values are monitored and reported only for processes loaded in the memory of the server node you are connected to.
You can configure two types of thresholds: Warning and error thresholds. Process instances that exceed the error threshold are suspended and further instantiations are denied. These actions are logged in the Business Log and the AS Java Log.