INC-173663 · Issue 651302
Resolved Push Node Daily Information exception
Resolved in Pega Version 8.7
The "Push Nodes Info Daily" agent was generating an exception on each of the nodes. This has been resolved by enhancing the PegaAESRemote code to handle the exception and get the node info locally, then push it to the console when it is not able to get it via the cluster management API.
INC-174296 · Issue 650756
Delayed JS/DF initialization failures will trigger alert
Resolved in Pega Version 8.7
In order to ensure better cluster monitoring, a PEGA0102 alert has been added for job registration failure that will be triggered if there are startup issues. The logging will include the JOB_NAME for improved troubleshooting.
INC-174298 · Issue 650259
Instance count logic updated
Resolved in Pega Version 8.7
A performance issue was seen during upgrade that resembled an upgrade hang. This was caused by a combination of incorrect logic in DDLGenerator.getInstanceCountForClass() around counting instances of 'core' classes and all of the site history-data- tables being mapped to the same table that had 1.4+ billion rows. This behavior has been addressed with more correct query logic while performing instance counts. In addition, instance count will be supressed during command line invocations (prpcUtils, platform upgrade).
INC-174567 · Issue 651121
Permissions added to handle Openshift installer image
Resolved in Pega Version 8.7
When running the install process on an Openshift test cluster, the process failed with a permissions error while attempting to download the postgresql-42.2.12.jar. This has been resolved by ensuring the root group can write to the distribution files.
INC-174612 · Issue 659248
Queue Processor threads explicitly cleared before new interaction
Resolved in Pega Version 8.7
Queue Processor was not clearing already evaluated freshness caches before running an activity, potentially causing a stale data page to be processed. This has been resolved by explicitly clearing the thread on a new interaction by invoking ((IPRThread) thread).clearOnNewInteraction.
INC-174625 · Issue 655242
Admin Studio will consider cluster protocol when returning listener status
Resolved in Pega Version 8.7
When using a few nodes in standalone mode for BIX extract combined with server nodes using Hazelcast, opening the admin studio pages with service discovery caused an error to be thrown. This was traced to the system writing an entry to pr_sys_statusnodes table as an embedded node whenever a BIX extract was triggered, causing those standalone nodes to be incorrectly considered by the listener landing page. This has been resolved by configuring the system to either return the local member when the cluster protocol is standalone or to return all Hazelcast members if the cluster protocol is Hazelcast.
INC-175197 · Issue 651114
Permissions added to handle Openshift installer image
Resolved in Pega Version 8.7
When running the install process on an Openshift test cluster, the process failed with a permissions error while attempting to download the postgresql-42.2.12.jar. This has been resolved by ensuring the root group can write to the distribution files.
INC-175205 · Issue 652531
Agent restart made more resilient
Resolved in Pega Version 8.7
During a timeout outage, agents intermittently encountered a NoClassDefFound error and were disabled. After the database connection was restored, the agents were not automatically restarting. This has been resolved by making the code more resilient to errors; agent will be restarted when a temporary issue is detected, and the restart will be immune to most exceptions.
INC-177512 · Issue 657015
Hazelcast packages expanded for Java9+ with kubernetes
Resolved in Pega Version 8.7
Hazelcast warnings were seen in cluster logs when Hazelcast was run in embedded mode or c/s mode on a java modular environment i.e. java 9+ which noted that performance and functional impact issues may result if certain internal modules of java are not given reflection access. This update provides the necessary access to some additional java internal modules/packages per the Hazelcast recommendation.
INC-177993 · Issue 658726
Schema packaging updated for better backwards compatibility
Resolved in Pega Version 8.7
After installing a hotfix, attempting to install another download which contained the same hotfix as a dependent resulted in the notification that schema changes were required and the message "ALTER TABLE pegadata.pr_archival_class_dependency ADD CONSTRAINT pr_archival_class_de_1812_PK PRIMARY KEY ("pzinskey")" was generated. Because the dependency already existed, attempting to install the hotfix failed until the constraint was manually removed from the database. Investigation showed this was caused by a difference in how schema was being generated for newer hotfixes vs older versions of Pega, and has been resolved by updating the schema packager and fixing the single col primary keys for Pega version 8.3 and lower.