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

Logfile error "detected large array in iterator"

SA-1448

Summary



You see the following error message in the PegaRULES.log file:

2014-09-17 14:31:33,436 [fault (self-tuning)'] [TABTHREAD3] 
(internal.clipboard.PropertySet) ERROR
 - detected large array in iterator: 2421, from page Declare_StaticData.ResultsLookup of size 2421

Why is the error reported?

Error Messages



detected large array in iterator: 2421, from page Declare_StaticData.ResultsLookup of size 2421


Steps to Reproduce



Run the rule which references ResultsLookup


Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules.
A diagnostic warning is output as an ERROR for large arrays.


Resolution



The explanation for this behavior is as follows: 
This is not an ERROR but more of a DEBUG or INFO as the declare page continues to load and writes this log entry when the list size is > 1000 to alert the requestor to check the size of the declare page if it can be reduced.
 

This issue is resolved through the following local change:

Update prlogging.xml to set FATAL level for com.pega.pegarules.data.internal.clipboard.PropertySet so ERROR is suppressed (this is the only log entry in the class)

Add the following in the prlogging.xml

<category name="com.pega.pegarules.data.internal.clipboard.PropertySet">
<priority value="fatal"/>
</category>

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