Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Seri Charoensri (chars1)
PEGA
Senior System Architect
Pegasystems Inc.
AU
chars1 Member since 2015 49 posts
PEGA
Posted: Jan 11, 2016
Last activity: Apr 13, 2016
Posted: 11 Jan 2016 6:58 EST
Last activity: 13 Apr 2016 2:14 EDT
Closed

AES Enterprise Health is not showing up and other issues

Hello,

    My client is currently implementing AES with AES 07.01.jar and has a few issues

AES_07.01-2013-12-20.png

1. The Enterprise Health is not showing any nodes (there should be 3 nodes listed in the Dropdown)?

Enterprise Health Clusters.png

I checked the pegaam_cluster_data and PegaAES-Data-Nodes class, both contain all the valid node name and id

pegaam_cluster_data.png

Show More

Hello,

    My client is currently implementing AES with AES 07.01.jar and has a few issues

AES_07.01-2013-12-20.png

1. The Enterprise Health is not showing any nodes (there should be 3 nodes listed in the Dropdown)?

Enterprise Health Clusters.png

I checked the pegaam_cluster_data and PegaAES-Data-Nodes class, both contain all the valid node name and id

pegaam_cluster_data.png

PeagaAES-Data-Nodes.png

What I can see the cluster query statement is per below and the PegaAES-Data-Indicator has no data.

SELECT "PC0".ClusterName AS "ClusterName" , "PC0".ProductionLevel AS "ProductionLevel" , "PC0".ClusterURL AS "ClusterURL" , "PC0".pyLabel AS "pyLabel" , "PC0".pzInsKey AS "pzInsKey" FROM rules.pegaam_cluster_data "PC0" INNER JOIN ( SELECT DISTINCT "CLINFO".ClusterName AS "SRCOL1" FROM rules.pegaam_indicator "CLINFO" WHERE ( UPPER("CLINFO".ClusterName) IN ('DEV' , 'SIT' , 'SANDPIT' ) ) AND "CLINFO".pxObjClass = 'PegaAES-Data-Indicator' ) "CLINFO" ON ( ( "CLINFO".SRCOL1 = "PC0".ClusterName ) AND "PC0".pxObjClass = 'PegaAES-Data-Cluster' ) ORDER BY 1 ASC

<DEV> <SANDPIT> <SIT> <PegaAES-Data-Indicator> <PegaAES-Data-Cluster>

Why are there no records for Indicators ? When are these created ? Auto or Manual ?

2. Only Alert messages show up in the dashboard, not exception messages?.  The

Hightest-Alert but no Exception.png

I can see the pegaam_exception table contains data sent from the monitored nodes.  But why the "High-Return Exception Action Items" shows no data.

3. The call back to get snapshot also fails.   From what I read up AES reaches back to monitored nodes via MBean operations to get info about alert origins, daily perf stats (LogUsage), production level, etc

Do we need to have the monitored node open up specific port for JMX, how does the call back work?

AES connectivity.png

2016-01-08 00:01:14,180 [   PegaRULES-Batch-2] [  STANDARD] [                    ] [           AES:07.10] (      internal.mgmt.Executable) ERROR Rule-Connect-SOAP.PegaAES-Data-RSSnapshot.GetRuleSetSnapshot  - Exception

com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed

at com.pegarules.generated.activity.ra_action_invokeaxis_3da0d7301b5c63bb26382db9d78337c3.step9_circum0(ra_action_invokeaxis_3da0d7301b5c63bb26382db9d78337c3.java:1385)

at com.pegarules.generated.activity.ra_action_invokeaxis_3da0d7301b5c63bb26382db9d78337c3.perform(ra_action_invokeaxis_3da0d7301b5c63bb26382db9d78337c3.java:205)

at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)

at com.pegarules.generated.activity.ra_action_invoke_5e9e0cecbbfdfa9a2b1306e703ec4af8.step8_circum0(ra_action_invoke_5e9e0cecbbfdfa9a2b1306e703ec4af8.java:1032)

at com.pegarules.generated.activity.ra_action_invoke_5e9e0cecbbfdfa9a2b1306e703ec4af8.perform(ra_action_invoke_5e9e0cecbbfdfa9a2b1306e703ec4af8.java:189)

at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)

at com.pegarules.generated.activity.ra_action_getrulesetsnapshot_2850390d5b1ce36cbd89eb174287f69f.step4_circum0(ra_action_getrulesetsnapshot_2850390d5b1ce36cbd89eb174287f69f.java:473)

at com.pegarules.generated.activity.ra_action_getrulesetsnapshot_2850390d5b1ce36cbd89eb174287f69f.perform(ra_action_getrulesetsnapshot_2850390d5b1ce36cbd89eb174287f69f.java:137)

at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)

at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10450)

at com.pegarules.generated.activity.ra_action_collectrulesetsnapshotsforcluster_ee9ed2c085f153dbdbe4aa0cfbb483fd.step3_circum0(ra_action_collectrulesetsnapshotsforcluster_ee9ed2c085f153dbdbe4aa0cfbb483fd.java:540)

at com.pegarules.generated.activity.ra_action_collectrulesetsnapshotsforcluster_ee9ed2c085f153dbdbe4aa0cfbb483fd.perform(ra_action_collectrulesetsnapshotsforcluster_ee9ed2c085f153dbdbe4aa0cfbb483fd.java:103)

at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)

at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10450)

at com.pegarules.generated.activity.ra_action_collectrulesetsnapshots_82411a6742e20307c9e157e5a5f0e08f.step2_circum0_PegaAES_Data_Cluster(ra_action_collectrulesetsnapshots_82411a6742e20307c9e157e5a5f0e08f.java:324)

at com.pegarules.generated.activity.ra_action_collectrulesetsnapshots_82411a6742e20307c9e157e5a5f0e08f.perform(ra_action_collectrulesetsnapshots_82411a6742e20307c9e157e5a5f0e08f.java:106)

at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)

at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:719)

at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:600)

at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:885)

at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1177)

at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:926)

at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:825)

at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:618)

at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991)

at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532)

at java.lang.Thread.run(Thread.java:744)

Caused by: SOAP service [PegaAESRemote][RuleData][GetRulesetSnapshot] failed:PRRuntimeError

2016-01-08 00:01:14,183 [   PegaRULES-Batch-2] [  STANDARD] [                    ] [           AES:07.10] (PegaAES_Data_RSSnapshot.Action) ERROR   - GetRuleSetSnapshot: Failed for designated node 34b4a81266ca689bb5d1ee9160222d70 for cluster SANDPIT with connection string http://DRSDEVPGA702.tmc.rta.nsw.gov.au/prweb/PRSOAPServlet

4.  AES agents has error below (see the attached file) How do I resolve the exception?

Exception at 20160101T073036.329 GMT: java.lang.IllegalStateException: Internal state is compromised; cannot write out application hierarchy and/or rulesets at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.populateApplicationRuleHierarchy(GlobalContextCache.java:1631) at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.populateApplicationRuleHierarchy(GlobalContextCache.java:1939) at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.populateApplicationRuleHierarchy(GlobalContextCache.java:1960) at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.writeApplicationInfoToDatabase(GlobalContextCache.java:1298) at com.pega.pegarules.session.internal.authorization.context.custom.ManagedApplicationContext.updateDBRSLAndAppStack(ManagedApplicationContext.java:843) at com.pega.pegarules.session.internal.authorization.context.custom.ManagedApplicationContext.updateToParent(ManagedApplicationContext.java:425) at com.pega.pegarules.session.internal.authorization.context.custom.ManagedApplicationContext.getChangeCount(ManagedApplicationContext.java:385) at com.pega.pegarules.session.internal.authorization.context.AbstractApplicationContext.getAppInfo(AbstractApplicationContext.java:43) at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.populateApplicationRuleHierarchy(GlobalContextCache.java:1955) at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.writeApplicationInfoToDatabase(GlobalContextCache.java:1298) at com.pega.pegarules.session.internal.authorization.context.custom.ManagedApplicationContext.updateDBRSLAndAppStack(ManagedApplicationContext.java:843) at com.pega.pegarules.session.internal.authorization.context.custom.ManagedApplicationContext.&lt;init&gt;(ManagedApplicationContext.java:102) at com.pega.pegarules.session.internal.authorization.context.custom.CustomApplicationContext.&lt;init&gt;(CustomApplicationContext.java:75) at com.pega.pegarules.session.internal.authorization.context.ContextUtils.ensureCustomizable(ContextUtils.java:973) at com.pega.pegarules.session.internal.authorization.Authorization.alterRuleSetList(Authorization.java:1034) at com.pega.pegarules.session.internal.authorization.Authorization.alterRuleSetList(Authorization.java:1027) at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:758) at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1177) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:926) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:825) at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:618) at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991) at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532) at java.lang.Thread.run(Thread.java:744) Caused by: com.pega.pegarules.pub.PRRuntimeException: caught exception during autocommit check at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.returnConnection(ConnectionManagerImpl.java:2228) at com.pega.pegarules.data.internal.access.ThreadConnectionStoreImpl.returnConnection(ThreadConnectionStoreImpl.java:504) at com.pega.pegarules.data.internal.access.RDBPageResultPackager.close(RDBPageResultPackager.java:897) at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6496) at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6429) at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6410) at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.doesTopAppHashNeedToBeInsertedIntoFlattenedHierarchy(GlobalContextCache.java:1878) at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.populateApplicationRuleHierarchy(GlobalContextCache.java:1603) ... 23 more Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190) at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(SQLServerConnection.java:388) at com.microsoft.sqlserver.jdbc.SQLServerConnection.getAutoCommit(SQLServerConnection.java:1909) at org.apache.tomcat.dbcp.dbcp.DelegatingConnection.getAutoCommit(DelegatingConnection.java:337) at org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.getAutoCommit(PoolingDataSource.java:235) at com.pega.pegarules.data.internal.access.DatabaseConnectionImpl.getAutoCommit(DatabaseConnectionImpl.java:806) at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.returnConnection(ConnectionManagerImpl.java:2221) ... 30 more




5. Would upgrade to the AES 07.13 (AES_07_13_01.jar) resolve most of the issues above, if so can I simply import the new jar on top?

Thank you in advance...


Show Less
To see attachments, please log in.
Pega Customer Service
Updates

Posted: 8 years ago
Posted: 11 Jan 2016 7:05 EST
Arvind Malav (malaa) Technical Manager
Pegasystems Inc.
IN

Can you please share the screenshot from Monitored node by following below path:

Pega Button --> Systen --> Settings --> Predictive Diagnostic Cloud

To see attachments, please log in.
Posted: 8 years ago
Posted: 11 Jan 2016 7:38 EST
Seri Charoensri (chars1)
PEGA
Senior System Architect
Pegasystems Inc.
AU

Hi Arvind,

My understanding is PDC only relevant if we send Health and Alert to the Pega Diagnostic Cloud? Here we have AES hosted locally... ?

pdc.png

To see attachments, please log in.
Posted: 8 years ago
Posted: 11 Jan 2016 7:55 EST
Seri Charoensri (chars1)
PEGA
Senior System Architect
Pegasystems Inc.
AU

OK, would I need to set this up on the monitored nodes? (and not the AES node).  So far the prlogging.xml has this setting to send SOAP msg to AES.  Do I need to add the URL to the monitored nodes...

To see attachments, please log in.
Posted: 8 years ago
Posted: 11 Jan 2016 8:11 EST
Arvind Malav (malaa) Technical Manager
Pegasystems Inc.
IN

Yes, you need to configure PDC on Monitored nodes and below value should be given:

http//AEShostingserver:port/prweb/PRSOAPServlet

To see attachments, please log in.
Posted: 8 years ago
Posted: 11 Jan 2016 8:28 EST
Seri Charoensri (chars1)
PEGA
Senior System Architect
Pegasystems Inc.
AU

Hi Arvind,

So far the prlogging.xml has the setting to send alert and exception to the AES node.  I agree that the Pega Button --> Systen --> Settings --> Predictive Diagnostic Cloud configuration is a new and effective way to change the endpoint, but so far the prlogging.xml has the setting and still not able see the Exception messages and Heath also does not show the monitored node.

I noted that agents on AES nodes has lots of errors which I don't know how to resolve.  Please take a look at the attached file - AES agent error.html.

To see attachments, please log in.
Posted: 8 years ago
Posted: 11 Jan 2016 8:25 EST
Sammeta (PrashantSammeta)

Either prlogging or landing page is enough you don't need two.

If prlogging is already setup can you check the below things:

On AES side:

Ask customer to check if 'Monitor Health Status' agent is running fine. (Use SMA)

Also there are two classes which can be set to Debug level to check if there are any problems with AES monitoring health status:

com.pega.pegarules.monitor.internal.context.ManagementDaemonImpl (On Monitored Node)

Rule_Obj_Activity.parseHLTH0001.PegaAES_Data_Alert.Action (On AES side)

Send the log files after enabling these.

You can also send prconfig.xml and prlogging.xml to see exact configuration.

To see attachments, please log in.
Posted: 8 years ago
Posted: 11 Jan 2016 8:32 EST
Seri Charoensri (chars1)
PEGA
Senior System Architect
Pegasystems Inc.
AU

OK thanks, we enable the debug tomorrow and send the log over.  Just on the SMA, please see the attached AES agent error.  I do NOT know how to resolve this error so that I can get the AES agents started again..

To see attachments, please log in.
Posted: 8 years ago
Posted: 11 Jan 2016 8:36 EST
Sammeta (PrashantSammeta)

You said prlogging.xml has setting to send alert and exception. Does this mean it is not configured to send health?

If not please configure it and then check if you get nodes in enterprise health. (you can do the log enabling later, if you don't get the enterprise health).

To see attachments, please log in.
Posted: 8 years ago
Updated: 8 years ago
Posted: 11 Jan 2016 8:53 EST
Updated: 11 Jan 2016 8:58 EST
Seri Charoensri (chars1)
PEGA
Senior System Architect
Pegasystems Inc.
AU

So far the  AES_Node_Configuration_Guide_71_1.pdf ohly mentioned two appenders one for Alert and another is for Exception.  How do you configure to send Health info?

Step 6. Update the prconfig.xml file to enable updates to the AES Enterprise Health monitor is for V5.3, V5.4 SP1 and SP2 only.

Do  I need to do the configure for health on the PDC setting?

<!-- Add the ALERT-ASYNC appender to propagate alerts to the ALERT-AES-SOAP appender: -->

<appender name="ALERT-ASYNC" class="com.pega.apache.log4j.AsyncAppender">

<param name="BufferSize" value="512"/>

<param name="Blocking" value="false"/>

<filter class="com.pega.apache.log4j.varia.LevelMatchFilter">

<param name="LevelToMatch" value="ALERT"/>

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

</filter>

<filter class="com.pega.apache.log4j.varia.DenyAllFilter"/>

<appender-ref ref="ALERT"/>

<appender-ref ref="ALERT-AES-SOAP"/>

</appender>

<!-- Add the ALERT-AES-SOAP appender (among the other appender definitions): -->

<appender name="ALERT-AES-SOAP" class="com.pega.pegarules.priv.util.SOAPAppenderPega">

<param name="BufferSize" value="512"/>

<param name="Blocking" value="false"/>

Show More

So far the  AES_Node_Configuration_Guide_71_1.pdf ohly mentioned two appenders one for Alert and another is for Exception.  How do you configure to send Health info?

Step 6. Update the prconfig.xml file to enable updates to the AES Enterprise Health monitor is for V5.3, V5.4 SP1 and SP2 only.

Do  I need to do the configure for health on the PDC setting?

<!-- Add the ALERT-ASYNC appender to propagate alerts to the ALERT-AES-SOAP appender: -->

<appender name="ALERT-ASYNC" class="com.pega.apache.log4j.AsyncAppender">

<param name="BufferSize" value="512"/>

<param name="Blocking" value="false"/>

<filter class="com.pega.apache.log4j.varia.LevelMatchFilter">

<param name="LevelToMatch" value="ALERT"/>

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

</filter>

<filter class="com.pega.apache.log4j.varia.DenyAllFilter"/>

<appender-ref ref="ALERT"/>

<appender-ref ref="ALERT-AES-SOAP"/>

</appender>

<!-- Add the ALERT-AES-SOAP appender (among the other appender definitions): -->

<appender name="ALERT-AES-SOAP" class="com.pega.pegarules.priv.util.SOAPAppenderPega">

<param name="BufferSize" value="512"/>

<param name="Blocking" value="false"/>

<param name="EndPointURL" value="http://AESNode:Port/prweb/PRSOAPServlet" />

<param name="Mode" value="ALERT" />

<param name="AllowLiveChanges" value="false"/>

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

<layout class="com.pega.apache.log4j.PatternLayout">

<param name="ConversionPattern" value="%m%n" />

</layout>

</appender>

<!-- Add the ASYNC appender to propagate messages to the EXCEPTION-AES-SOAP appender: -->

<appender name="ASYNC" class="com.pega.apache.log4j.AsyncAppender">

<param name="BufferSize" value="512"/> <param name="Blocking" value="false"/>

<filter class="com.pega.apache.log4j.varia.LevelMatchFilter">

<param name="LevelToMatch" value="ALERT"/>

<param name="AcceptOnMatch" value="false"/>

</filter>

<appender-ref ref="CONSOLE"/>

<appender-ref ref="PEGA"/>

<appender-ref ref="EXCEPTION-AES-SOAP"/>

</appender>

<!-- Add the EXCEPTION-AES-SOAP appender (among the other appender definitions): -->

<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://AESNode:Port/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>

<!-- end AES config -->


Show Less
To see attachments, please log in.
Posted: 8 years ago
Posted: 11 Jan 2016 7:20 EST
Rajiv Nistala (nistr) Senior Manager - Engineering
Pegasystems
IN

Please share the following

1) Which version of Pega 7 did you use to load AES 07.01.jar?

2) Which version of Pega are you monitoring using this AES system?

Did you following the install and upgrade guide for AES 7.1 - https://community.pega.com/documents/autonomic-event-services-aes-71-installation-and-upgrade-guide?

Can you check the following options on the administration tab?

To see attachments, please log in.
Posted: 8 years ago
Posted: 11 Jan 2016 7:52 EST
Seri Charoensri (chars1)
PEGA
Senior System Architect
Pegasystems Inc.
AU

Hi Ravij

1) Which version of Pega 7 did you use to load AES 07.01.jar?

    We upgraded Pega 6 to Pega 7.1.7

2) Which version of Pega are you monitoring using this AES system?

    The monitored nodes also have been upgraded from Pega 6 yo Pega 7.1.7.

I believe the AES 07.01.jar was loaded after the Pega upgrade to 7.1.7 platform and so the installation guide was used.

I am new to AES, not sure what to expect.  What I just did was adding aesmanager to manage the Dev, SandPit and SIT nodes.

Manage Operator Clusters.png

Display Operators by Cluster.png

Show More

Hi Ravij

1) Which version of Pega 7 did you use to load AES 07.01.jar?

    We upgraded Pega 6 to Pega 7.1.7

2) Which version of Pega are you monitoring using this AES system?

    The monitored nodes also have been upgraded from Pega 6 yo Pega 7.1.7.

I believe the AES 07.01.jar was loaded after the Pega upgrade to 7.1.7 platform and so the installation guide was used.

I am new to AES, not sure what to expect.  What I just did was adding aesmanager to manage the Dev, SandPit and SIT nodes.

Manage Operator Clusters.png

Display Operators by Cluster.png

Display Operators by Cluster2.png

Cluster Settings.png


Show Less
To see attachments, please log in.
Posted: 8 years ago
Posted: 11 Jan 2016 9:38 EST
Arvind Malav (malaa) Technical Manager
Pegasystems Inc.
IN

Supporting Rajiv, we had a customer who faced issue (AES is no longer displaying graphs or alerts). He was using first release of AES 7 and issue got resolved after upgrading to latest AES, ie, AES 7.1.7

To see attachments, please log in.
Posted: 8 years ago
Posted: 11 Jan 2016 12:33 EST
Rajiv Nistala (nistr) Senior Manager - Engineering
Pegasystems
IN

I am suggesting based on the fact that AES 7.1.7 does fix some issues noticed in AES 7.1. Before we get to AES 7.1.7, it might be a good idea to check the logs on both sides to see if we are getting the data correctly or not. You could use TcpMon to check the SOAP messages being sent to and from AES 7.1.

Also, could you please check the Data-Admin-System-Settings instance "aessetting/perfstatmode" on the monitored side? This should be set to PULL.

There was mention that the monitored nodes have also been upgraded. We had an issue when AES 7.1 is monitoring Pega 6 nodes. Just wondering if that is still in play here.

To see attachments, please log in.
Posted: 8 years ago
Posted: 11 Jan 2016 18:34 EST
Seri Charoensri (chars1)
PEGA
Senior System Architect
Pegasystems Inc.
AU

Yes, the AES node was on Pega6 before and upgraded to Pega7.  I don't know if this has any impact.  The worst case is to have the client install a clean copy of Pega7.1.9 for AES.  Question, will we have the communication issues between different Pega 7.1.7 (monitored nodes) -> Pega 7.1.9 (AES)?

To see attachments, please log in.
Posted: 8 years ago
Posted: 11 Jan 2016 20:34 EST
Seri Charoensri (chars1)
PEGA
Senior System Architect
Pegasystems Inc.
AU

Hi Rajiv

  I think I will take the upgrade AES path from 7.10 to 7.13. 

  FYI the Data-Admin-System-Settings instance "aessetting/perfstatmode" on the monitored side is "PUSH".  I checked this in my local environment.  So I will leave this as "PUSH" on the monitored node to push data to AES node.

To see attachments, please log in.
Posted: 8 years ago
Updated: 8 years ago
Posted: 12 Jan 2016 1:33 EST
Updated: 12 Jan 2016 1:37 EST
Seri Charoensri (chars1)
PEGA
Senior System Architect
Pegasystems Inc.
AU

Hi Rajiv,

I reimported the new AES jar version and clicked "Upgrade".

It looks OK.  However, AES PegaRULES log file has lots of errors.  I don't know if I can just explain or justify those errors.  Need explanation on those errors.

I am not sure if I am getting the SQL errors e.g. Invalid object name 'pegaam_alert' - how come the alert messags still show up in the Dash board.

1. com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pegaam_alert'.

2016-01-12 15:23:34,123 [   PegaRULES-Batch-2] [  STANDARD] [                    ] [           AES:07.10] (l.access.ConnectionManagerImpl) ERROR   - Not returning connection 4 for database "pegadata" to the pool as it previously encountered the following error

User ID: System

Last SQL: select  avg(OTHERIOCOUNT) as "Avg",     sum(OTHERIOCOUNT) as "Total",     count(*) as "Count",    max(OTHERIOCOUNT) as "Max",    min(OTHERIOCOUNT) as "Min"     from pegaam_alert     where msgID = ? and ProblemCorrelation=?

com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pegaam_alert'.

  at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)

2. Problem #1, SQLState S0002, Error code 208: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pegaam_alert'.

Show More

Hi Rajiv,

I reimported the new AES jar version and clicked "Upgrade".

It looks OK.  However, AES PegaRULES log file has lots of errors.  I don't know if I can just explain or justify those errors.  Need explanation on those errors.

I am not sure if I am getting the SQL errors e.g. Invalid object name 'pegaam_alert' - how come the alert messags still show up in the Dash board.

1. com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pegaam_alert'.

2016-01-12 15:23:34,123 [   PegaRULES-Batch-2] [  STANDARD] [                    ] [           AES:07.10] (l.access.ConnectionManagerImpl) ERROR   - Not returning connection 4 for database "pegadata" to the pool as it previously encountered the following error

User ID: System

Last SQL: select  avg(OTHERIOCOUNT) as "Avg",     sum(OTHERIOCOUNT) as "Total",     count(*) as "Count",    max(OTHERIOCOUNT) as "Max",    min(OTHERIOCOUNT) as "Min"     from pegaam_alert     where msgID = ? and ProblemCorrelation=?

com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pegaam_alert'.

  at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)

2. Problem #1, SQLState S0002, Error code 208: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pegaam_alert'.

2016-01-12 15:23:34,124 [   PegaRULES-Batch-2] [  STANDARD] [                    ] [           AES:07.10] (nvokeODBCSQL._baseclass.Action) ERROR   - Error in RDB-Open

com.pega.pegarules.pub.database.DatabaseException: There was a problem getting a list: code: 208 SQLState: S0002 Message: Invalid object name 'pegaam_alert'.

From: (B0842D94701E35FB0A8E633FEBBAB4395)

  SQL: select  avg(OTHERIOCOUNT) as "Avg",     sum(OTHERIOCOUNT) as "Total",     count(*) as "Count",    max(OTHERIOCOUNT) as "Max",    min(OTHERIOCOUNT) as "Min"     from pegaam_alert     where msgID = ? and ProblemCorrelation=?

  SQL Inserts: <PEGA0001> <DEV:Browser Time:3ae12886517c3ef7df2d742f1b297d>

Caused by SQL Problems.

Problem #1, SQLState S0002, Error code 208: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pegaam_alert'.

3.

2016-01-12 15:28:49,240 [   PegaRULES-Batch-2] [  STANDARD] [                    ] [           AES:07.10] (Action_QueryPerformance.Action) ERROR   - Unable to load list of PRPC tables.

2016-01-12 15:28:49,244 [   PegaRULES-Batch-2] [  STANDARD] [                    ] [           AES:07.10] (Action_QueryPerformance.Action) ERROR   - Unable to load list of PRPC stored procedures.

2016-01-12 15:28:49,248 [   PegaRULES-Batch-2] [  STANDARD] [                    ] [           AES:07.10] (Action_QueryPerformance.Action) ERROR   - Unable to load list of PRPC Rulesets.

4. ExecuteGetIndexInfo Error (but the node ID is correct)

016-01-12 15:28:52,283 [   PegaRULES-Batch-2] [  STANDARD] [                    ] [           AES:07.10] (.PegaAES_Data_IndexInfo.Action) ERROR   - ExecuteGetIndexInfo: Error sending to connection. Please check connection in node: 742848a5278681d07681caf3aeb5e602 Conn: http://DRSDEVPGA701.tmc.rta.nsw.gov.au/prweb/PRSOAPServlet

2016-01-12 15:28:54,260 [   PegaRULES-Batch-2] [  STANDARD] [                    ] [           AES:07.10] (.PegaAES_Data_IndexInfo.Action) ERROR   - ExecuteGetIndexInfo: Error sending to connection. Please check connection in node: 742848a5278681d07681caf3aeb5e602 Conn: http://DRSDEVPGA701.tmc.rta.nsw.gov.au/prweb/PRSOAPServlet

5.

2016-01-12 15:39:22,917 [   PegaRULES-Batch-2] [  STANDARD] [                    ] [           AES:07.13] (egaAES_Data_AlertOrigin.Action) ERROR   - ExecuteGetActivityData: Error. Cluster: DEV Node: 742848a5278681d07681caf3aeb5e602 Connection: http://DRSDEVPGA701.tmc.rta.nsw.gov.au/prweb/PRSOAPServlet InsKey: RULE-OBJ-SUMMARYVIEW INDEX-REFERENCE PZPROPERTIESTOPUSEDINREPORTS!ALL #20130919T010735.188 GMT ID: DB-620 Msg:

2016-01-12 15:39:22,918 [   PegaRULES-Batch-2] [  STANDARD] [                    ] [           AES:07.13] (egaAES_Data_AlertOrigin.Action) ERROR   - Rule data lookup failed for: DB-620 -- please verify that PegaAESRemote application has been appropriately installed and configured on the monitored system.

6.

016-01-12 15:52:56,116 [   PegaRULES-Batch-5] [  STANDARD] [                    ] [           AES:07.13] (l.access.ConnectionManagerImpl) ERROR   - Not returning connection 1 for database "pegadata" to the pool as it previously encountered the following error

User ID: System

Last SQL: SELECT "PC0".pyEmail1 AS "pyEmail1" , "PC0".pzInsKey AS "pzInsKey" FROM rules.pegaam_email_recipient "PC0" WHERE  (  ( "PC0".ClusterName = ?  OR "PC0".ClusterName = ?  )  AND  ( "PC0".pyEmail1Type = ?  OR "PC0".pyEmail1Type = ?  )  AND  (  ( (CASE       WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) >= 0 THEN     (CASE   WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) = 7      THEN 1 ELSE              ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +1 END)              ELSE ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +8 END) = ?  AND rules.pr_read_from_stream('.DaysOfWeekSubscribedFor.Sunday', "PC0".pzInsKey, "PC0".pzPVStream) = ?  )  OR  ( (CASE       WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) >= 0 THEN     (CASE   WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) = 7      THEN 1 ELSE              ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +1 END)              ELSE ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +8 END) = ?  AND rules.pr_read_from_stream('.DaysOfWeekSubscribedFor.Monday', "PC0".pzInsKey, "PC0".pzPVStream) = ?  )  OR  ( (CASE       WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) >= 0 THEN     (CASE   WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) = 7      THEN 1 ELSE              ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +1 END)              ELSE ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +8 END) = ?  AND rules.pr_read_from_stream('.DaysOfWeekSubscribedFor.Tuesday', "PC0".pzInsKey, "PC0".pzPVStream) = ?  )  OR  ( (CASE       WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) >= 0 THEN     (CASE   WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) = 7      THEN 1 ELSE              ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +1 END)              ELSE ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +8 END) = ?  AND rules.pr_read_from_stream('.DaysOfWeekSubscribedFor.Wednesday', "PC0".pzInsKey, "PC0".pzPVStream) = ?  )  OR  ( (CASE       WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) >= 0 THEN     (CASE   WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) = 7      THEN 1 ELSE              ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +1 END)              ELSE ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +8 END) = ?  AND rules.pr_read_from_stream('.DaysOfWeekSubscribedFor.Thursday', "PC0".pzInsKey, "PC0".pzPVStream) = ?  )  OR  ( (CASE       WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) >= 0 THEN     (CASE   WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) = 7      THEN 1 ELSE              ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +1 END)              ELSE ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +8 END) = ?  AND rules.pr_read_from_stream('.DaysOfWeekSubscribedFor.Friday', "PC0".pzInsKey, "PC0".pzPVStream) = ?  )  OR  ( (CASE       WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) >= 0 THEN     (CASE   WHEN ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? ) = 7      THEN 1 ELSE              ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +1 END)              ELSE ((DATEPART(dw,? +@@DATEFIRST-2)%7)+2 -? )  +8 END) = ?  AND rules.pr_read_from_stream('.DaysOfWeekSubscribedFor.Saturday', "PC0".pzInsKey, "PC0".pzPVStream) = ?  )  )  )  AND "PC0".pxObjClass = ?

com.microsoft.sqlserver.jdbc.SQLServerException: Operand type clash: datetime2 is incompatible with tinyint

I will attach the log next.


Show Less
To see attachments, please log in.
Posted: 8 years ago
Posted: 13 Apr 2016 2:14 EDT
Binh Nguyen (BinhNguyen)
Department of home affairs
Pega Administrator
Department of home affairs
AU

I have AES installed but none of the node show up on the health console, do I have to installed AES.jar file to all the monitor node?

I have update the PDC setting in the pega nodes to point to the AES Server

I am using pega 7.1.9 and AES 7.1.7

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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