Hello,
We configured the BPM Memory Threshold on SAP PO 7.5 SP 18 & 20 but it doesn't take any effects.
The disasterbrakes property of Galaxy Core Service is set to true (in NWA --> Configuration --> Infrastructure --> Java System Properties --> the Services tab --> the Galaxy Core Service).
We were testing different values as "Number of process instances per definition", "Total number of process instances" and "Number of token per process instance". Unfortunately during out tests we could see several times more BPM instances in the progress status than the above limits.
I couldn't find anything in the business log but in the AS Java log I found entries like below:
com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException: Technical difficulties were experienced during process execution.
(...)
Caused by: java.lang.RuntimeException: BPMN process could not be started; maximum number of <our limit that we set> allowed active processes for model definition "<our process name>" (MOFID: <GUID>) reached; try again later
But as I've said it earlier, no process failed or was suspended, all of them were running concurrently and finished successfully (sic!).
What did we miss? Any hints?
Regards,
Andrzej
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.