Support Article
Issue with updateaction-pegaToInteger() causing memory growth
SA-8047
Summary
TotalKPI .pegaToInteger() Invalid number format (was 4116830774) error is seen frequently in AES Server log file.
Error Messages
com.pega.pegarules.pub.clipboard.InvalidValueException: PropertyValueInvalid TotalKPI .pegaToInteger() Invalid number format (was 4116830774)
at com.pega.pegarules.pub.clipboard.PRStringFormat.pegaToInteger(PRStringFormat.java:796)
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyBase.toInteger(ClipboardPropertyBase.java:3483)
at com.pegarules.generated.activity.ra_action_removeduplicateorigins_7c81f6109682e19f6c500813cc1d0066$1Origin.<init>(ra_action_removeduplicateorigins_7c81f6109682e19f6c500813cc1d0066.java:174)
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.
Resolution
This issue is resolved by hotfix item HFix-21354
Published January 31, 2016 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.