Support Article
FirstUseAssemblerException in AES logs due to SQLParser
SA-9870
Summary
Errors found in the log files when the AES manager is accessed. This is frequent in the logs whenever developer clicks Health or opens any report.
Error Messages
Caused by: com.pega.pegarules.pub.generator.FirstUseAssemblerException: Failed to compile generated Java com.pegarules.generated.activity.ra_action_processpcfsql_47e4592fdb1d89b4da6bd07288c8a014: ----------
1. ERROR in com/pegarules/generated/activity/ra_action_processpcfsql_47e4592fdb1d89b4da6bd07288c8a014.java (at line 245)
com.pega.aes.utils.sql.SQLParser parser = new com.pega.aes.utils.sql.SQLParser();
^^^^^^^^^^^^
com.pega.aes cannot be resolved to a type
----------
2. ERROR in com/pegarules/generated/activity/ra_action_processpcfsql_47e4592fdb1d89b4da6bd07288c8a014.java (at line 245)
com.pega.aes.utils.sql.SQLParser parser = new com.pega.aes.utils.sql.SQLParser();
^^^^^^^^^^^^
com.pega.aes cannot be resolved to a type
----------
2 problems (2 errors)
From: (A59C87D97B6C67934EF27F453DD3BBD60:PegaAES)
Also in the Monitored log user getting the below error.
2015-04-30 16:40:46,136 ERROR [STDERR] log4j:ERROR Exception in SOAPAppenderPega.sendEvent()
2015-04-30 16:40:46,136 ERROR [STDERR] log4j:ERROR Msg: SOAP service [PegaAES][Events][logAlert] failed:PRRuntimeError
2015-04-30 16:40:46,136 ERROR [STDERR] log4j:ERROR Cause: null
2015-04-30 16:40:46,356 ERROR [STDERR] log4j:ERROR Exception in SOAPAppenderPega.sendEvent()
2015-04-30 16:40:46,356 ERROR [STDERR] log4j:ERROR Msg: SOAP service [PegaAES][Events][logAlert] failed:PRRuntimeError
2015-04-30 16:40:46,356 ERROR [STDERR] log4j:ERROR Cause: null
2015-04-30 16:40:53,027 ERROR [STDERR] log4j:ERROR Exception in SOAPAppenderPega.sendEvent()
Steps to Reproduce
Click Health
(or)
Open any report
Root Cause
During AES installation, developer must import five .jar files into the PegaRULES database with the codeset name “pegaaes”.
Note:Obtain the jar files by running the query: select distinct pzjar from pr_engineclasses where pzcodeset='pegaaes'.
Pega-provided activity PegaAES-Data-UtilityObject fails to compile because it does not find the SQLParser class.
Resolution
This issue is resolved through the following Local-change:
For the PRPC engine to load the JAR files, add the Dynamic System Setting:
properties/com.pega.pegarules.bootstrap.codeset.version.pegaaes/default and value: 07-20-01 with Owning ruleset: Pega-Engine
Published May 25, 2015 - 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.