INC-159834 · Issue 632248
StackOverFlow logging improved
Resolved in Pega Version 8.5.4
Enhanced diagnostic logging information has been added to help find issues when StackOverFlow errors occur.
INC-161984 · Issue 638857
Web Tier busy threads released on timeout
Resolved in Pega Version 8.5.4
Tomcat Web Tier Busy Threads were not being correctly released, causing stability and performance problems that included health check pings not receiving a thread to service the request so the node was marked as bad, users were quiesced, and the node replaced. Investigation showed the 'put' on the blocking queue did not time out when the queue was full and waited indefinitely, keeping the thread blocked. To resolve this, the system will use 'offer' on the blocking queue instead of 'put' to force thread release on timeout. In addition, debug logs have been added to understand when the offer (or Put) does not succeed and the state of the queue that is causing this issue; the debug logs for class com.pega.pegarules.session.internal.serverpush.RoboticAutomationImpl should be enabled only if the thread busy issue is observed and for limited time window while actively debugging.
INC-164794 · Issue 637992
Apache Commons libraries updated
Resolved in Pega Version 8.5.4
Apache commons-codec has been updated to version 1.15 , and Apache commons-io has been updated to version 2.7.
INC-171587 · Issue 652187
Resolved Push Node Daily Information exception
Resolved in Pega Version 8.5.4
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-173162 · Issue 650794
Certificate match will use Subject Distinguished Name
Resolved in Pega Version 8.5.4
Signature verification was failing due to the system not finding the matching root certificate for the chain. The root certificate was in the trust store, but the system found a different certificate first and that other certificate (an intermediate certificate) was not considered a valid certificate for validating the whole certificate chain. This was traced to filtering on the Issuer Distinguished Name (DN) instead of the Subject DN and was due to intermediate certificates potentially having the same Issuer as a root certificate (e.g. if that root certificate was used to create the intermediate certificate). To resolve this, an update has been made to check the Subject DN instead of Issuer DN.
INC-174298 · Issue 650258
Instance count logic updated
Resolved in Pega Version 8.5.4
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).
SR-D48396 · Issue 520424
Hazelcast upgraded to resolve node startup issue
Resolved in Pega Version 8.1.8
Post data upgrade, the ADM tier failed to start and the error "java.lang.IllegalStateException: Node failed to start!" appeared. This was traced to a dormant bug in Hazelcast 3.11 that caused starting nodes to fail when the Hazelcast master node was shutting down, which was exposed by recent Pega changes made to enable parallel restarts of nodes in Cloud environments. Hazelcast delivered a fix for the parallel restart problem and the hotfixed jar has been merged into the platform.
SR-D52249 · Issue 515703
Resolved Oracle thread deadlock for Merge SQL
Resolved in Pega Version 8.1.8
After starting a large cluster and running it for a couple of days, Oracle Deadlocks started to appear due to resource contention during MERGE SQL execution on the PR_INDEX_REFERENCE database table. The "ORA-00060: deadlock detected while waiting for resource" ERROR occur continuously every 10 minutes during the "MasterForNewAgents" Daemon run. All JVMs are impacted by the ERROR/Deadlock. Investigation showed that even though the identified / problematic Data-Agent_queue instances were disabled for PegaAESRemote, the MERGE SQLs continued to fire. To resolve this, an update has been made so the system will skip the copy of rule reference property from RAQ, while creating DAQ.
SR-D55160 · Issue 520356
Namibia and Botswana added to Currency Symbol values
Resolved in Pega Version 8.1.8
Support has been added for the Namibia (en_NA) and Botswana (en_BW) locales in the default Currency Symbol values.
SR-D56527 · Issue 538302
DSS PegaAESREmote*ResetTableStats set to false
Resolved in Pega Version 8.1.8
In order to prevent an issue with resetting table stats that potentially impacts postgres in an unintended fashion, the DSS PegaAESREmote*ResetTableStats has been set to false.