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

Issue with updateaction-pegaToInteger() causing memory growth



TotalKPI .pegaToInteger() Invalid number format (was 4116830774) error is seen frequently in AES Server log file.

Error Messages PropertyValueInvalid    TotalKPI    .pegaToInteger()    Invalid number format (was 4116830774)
    at com.pegarules.generated.activity.ra_action_removeduplicateorigins_7c81f6109682e19f6c500813cc1d0066$1Origin.<init>(

Steps to Reproduce

PRPC System monitored by AES should generate ALERTs with TotalKPI values that are bigger than int limits. HTTP Stream size in byte Alerts for large stream Rules can generate these Alerts.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. 


This issue is resolved by hotfix item HFix-21354

Published January 31, 2016 - Updated December 2, 2021

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