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

Error in PegaRULES logs on AES server after JVM restart

SA-46545

Summary



Error in PegaRULES logs on Autonomic Event Services (AES) server after JVM restart. Agent failures occur after these errors and the application becomes inaccessible.

Error Messages



[10/8/17 5:15:16:412 EDT] 0000012e SystemOut O 2017-10-08 05:15:16,393 [ WebContainer : 8] [ STANDARD] [ AES:07.13] (l.library.LibraryMetadataCache) ERROR your_user|your_ip|SOAP|PegaAES|Events|logAlert|A9BE96750EC9BC550AF10D53B2D592917 - Problem invoking function: pega_wb_reportcontentbuilder.getSummarySelectClause--(Clipboa1c8bdf3ef5ded3c7270dc230673e8ee3
java.lang.ClassNotFoundException: com.pegarules.generated.getSummarySelectClause_071017_9C3u7uW0082PpEKvELeZjA
at com.pega.pegarules.internal.bootstrap.phase2.PRBaseLoader.findClass(PRBaseLoader.java:312)
at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:777)
at java.lang.ClassLoader.loadClass(ClassLoader.java:754)
at com.pega.pegarules.internal.bootstrap.phase2.PRBaseLoader.loadClass(PRBaseLoader.java:237)
at java.lang.ClassLoader.loadClass(ClassLoader.java:731)
at com.pega.pegarules.bootstrap.loader.PRAppLoader.loadClass(PRAppLoader.java:772)


Steps to Reproduce



Not Applicable


Root Cause



A defect in Pegasystems’ code or rules:

Following a restart, the Pega engine failed to prepare library definitions for use in a timely fashion (that is, before starting the processing of alerts from monitored Pega server).

The following message appears during Pega engine startup.
Preparing Rule-Utility-Library definitions for use.

but there isn't a message that confirms completing this preparation.
In Pega versions 7.2 and later versions libraries are created in advance using a different approach so this issue doesn't happen.

Resolution



Perform the following local-change:

Do not delete PegaRULES extract marker file upon AES server restart to prevent this issue from happening.

Suggest Edit

Published March 24, 2018 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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