SA-7061

Summary

Configured server PEGA 6.3 SP1 don't send any error info to AES 7.1. Alerts are visible normally. Health tab info are visible normally too.

Root Cause

The root cause of this problem is defect/misconfiguration in the PRPC operating environment. The customer was not able to see any exception messages being delivered to AES.

Resolution

This were several issues that were identified with the customers AES install.

1.

The main issue was resolved by the customer adding outputenabled to the prlogging.xml for exceptions and fixing their soap connection settings.

In the prlogging.xml in the <appender name="EXCEPTION-AES-SOAP" class="com.pega.pegarules.priv.util.SOAPAppenderPega"> section was missing the following param

<param name="OutputEnabled" value="true"/>

Add this to your configuration. As per the manual the section should look like this but changed to reflect your server address:

<appender name="EXCEPTION-AES-SOAP" class="com.pega.pegarules.priv.util.SOAPAppenderPega">
<param name="BufferSize" value="512"/>
<param name="Blocking" value="false"/>
<param name="EndPointURL" value="http://localhost:8080/prweb/PRSOAPServlet" />
<param name="Mode" value="exception" />
<param name="AllowLiveChanges" value="true" />
<param name="OutputEnabled" value="true"/>
<param name="ExceptionsOnly" value="true" />
<layout class="com.pega.apache.log4j.PatternLayout">
<param name="ConversionPattern"
value="%d{GMT}*%Y{instance_id}*%t*%c*%X{RequestorId}*%X{pegathread} *%X{app}*%X{userid}*%X{stack}*%m%n"/>
</layout>
</appender>

2.
The second issue was:

2014-11-07 11:46:06,990 [ WebContainer : 0] [ STANDARD] [ ] [ AES:07.10] (e.VirtualRuleTableDispatchImpl) ERROR your_server|127.0.0.1|SOAP|PegaAES|Events|logAlert|A463488D593A20F7549672E917589557E - failed to generate (Action) for keys: {pyClassName=PegaAES-Data-Alert, pxObjClass=Rule-Obj-Activity, pyActivityName=processdata}
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


This was resolved via dynamic system setting change:

1.Add a Dynamic System Setting for Pega-Engine.properties/com.pega.pegarules.bootstrap.codeset.version.pegaaes/default.
2.Specify the value 07-20-01.


3.

The third issue was:

From: (A0AC649693BAEDD8F6E433C7D67E766B6:PegaAES)
SQL: insert into RULES.pegaam_exception (CLUSTERNAME , GENERATEDDATETIME , OPERATORID , PROBLEMCORRELATION , PROBLEMCORRELATIONLABEL , PRTHREADNAME , PXCREATEDATETIME , PXINSNAME , PXOBJCLASS , PYLABEL , RELATEDRULEINSKEY , REQUESTORID , ROOTEXCEPTIONCLASS , ROOTEXCEPTIONMESSAGE , RULEAPPLICATION , SERVERID , SQLSTATECLASSCODE , SQLSTATECODE , THREADNAME , TOPLEVELEXCEPTIONCLASS , TOPLEVELEXCEPTIONMESSAGE , pzInsKey , pzPVStream) values (? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?)
SQL Inserts: <Cluster1> <2015-02-10 17:55:16.567> <<null>> <Cluster1:EXCEPTION:9ffdc470d039cc90907219634cbebfe2> <9ffdc470d039cc90907219634cbebfe2:com.sun.mail.smtp.SMTPAddressFailedExceptioncom.sun.mail.smtp.SMTPTransport.rcptTo!1145:!:> <STANDARD> <2015-02-10 17:55:16.573> <Cluster1:EXCEPTION:9FFDC470D039CC90907219634CBEBFE2!BB3F20EC5241E46C82A59CAD0C05B91CB!20150210T145516.567 GMT!82279> <PegaAES-Data-Exception> <<null>> <<null>> <BB3F20EC5241E46C82A59CAD0C05B91CB> <com.sun.mail.smtp.SMTPAddressFailedException> <553 sorry, relay denied.> <Your_app:01.01.01> <c074f1c8157f6c92d656b0c073d0b28a> <00> <00000> <WorkManager.PRPCWorkManager : 13> <javax.mail.SendFailedException> <Unexpected exception caught while trying to send an email message.> <<stream>> <PEGAAES-DATA-EXCEPTION Cluster1:EXCEPTION:9FFDC470D039CC90907219634CBEBFE2!BB3F20EC5241E46C82A59CAD0C05B91CB!20150210T145516.567 GMT!82279>

Caused by SQL Problems.
Problem #1, SQLState 72000, Error code 1502: java.sql.SQLException: ORA-01502: index 'RULES.PEGAAM_EXCEPTION_PK' or partition of such index is in unusable state


This was resolved by rebuilding the indexes.


4.

The final issue was that their SOAP urls were incorrect, which was resolved locally