Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Batch Data Flow causes CPU starvation when errors



User is having Pega 7.1.8 running with Apache Tomcat v6.0.28 on a local Windows OS and connecting to Oracle 11g. And, user is having Sun JDK 1.6.0_21 installed on this system.

The problem occurs each time an error is encountered and this is the observed behavior:
(1) The CPU utilization increases dramatically.
(2) The time to process is extended by a considerable margin for each error that is encountered.
(3) On occasions even at modest volume the environment (node) has been compromised. This has happened in both a local instance and a cloud instance in use for development. 

Error Messages

None. Specifically the error is reported via the Data Flow run control panel and following exception was reported:
Caused by: Strategy component Strategy___Result___Final___Output failed to execute: Strategy component WEBDataCollection failed to execute: PropertyValueInvalid null .pegaToDouble() Invalid number format (was 1.0)
at com.pegarules.generated.strategy.ra_action_adaptive_web_e7da7d9b2f2ffb6e758d299c85310908.executeStrategy___Result___Final___Output(
at com.pegarules.generated.strategy.ra_action_adaptive_web_e7da7d9b2f2ffb6e758d299c85310908.perform(
at com.pega.decision.dsm.strategy.CachedExternalRuleExecutor.doAction(
... 138 more
Caused by: Strategy component WEBDataCollection failed to execute: PropertyValueInvalid null .pegaToDouble() Invalid number format (was 1.0)
at com.pegarules.generated.strategy.ra_action_adaptive_web_e7da7d9b2f2ffb6e758d299c85310908.executeWEBDataCollection(
at com.pegarules.generated.strategy.ra_action_adaptive_web_e7da7d9b2f2ffb6e758d299c85310908.executeStrategy___Result___Final___Output(
... 140 more

Steps to Reproduce

Execute any Data Flow to process a batch of input data calling the decision logic (Strategy) that results in an error being detected that is a PRError being reported in the PRPC log file.

Root Cause

In Pega 7.1.8, following were the two issues:

1: In case decision Strategy contains lots of components, the java call stack is too deep and it takes a lot of time to generate and save it.
2: The "1.0" NumberFormatException.


Apply HFix-25366.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us