INC-172692 · Issue 650612
InsID will be derived from handle if null after update
Resolved in Pega Version 8.6.1
Updating from Pega 7.2.x to Pega 8.4.x failed with a null pointer exception in the “Upgrade Context” target. This was traced to a rule where the pxInsID was null. To resolve this, an update has been made to derive the InsID from handle when needed.
INC-173092 · Issue 648736
Handling added for multi-node concurrent access to conclusions
Resolved in Pega Version 8.6.1
A proposition update was triggered and heap memory jumped up and a thread dump was generated. A Pega0004 error was also generated at the same time. Investigation showed that many queries were getting fired on pr4_rule_sysgen table in a multi-node environment during RAP import. This caused database contention as more than 80 nodes were trying to load conclusions simultaneously. To resolve this, an update has been made to run an agent periodically to save conclusions into the database. This agent is configured to not run on multiple nodes simultaneously, which will avoid database contention issues from conclusions.
INC-173436 · Issue 648819
Performance improvement for Application Save: Node Level Data Pages
Resolved in Pega Version 8.6.1
As part of new functionality introduced in 8.3, data types defined in the application record will be turned into data objects on Application save. As part of this process node level pages are invalidated and reloaded and there is an explicit commit that marks the Application record as dirty and sends any calls for the application record to the database for fresh records. In a multi-node environment, the number of queries to get the application record being saved became exponentially higher and performance impacts were seen. This has been resolved by updating the system to skip eager loading of the data page definition when an access rule or application definition is saved.
INC-173895 · Issue 655916
ZMW adde to currency codes
Resolved in Pega Version 8.6.1
The Zambian Kwacha, "ZMW", has been added to the currencies code list in ENCurriencies.xml .
INC-174243 · Issue 655887
Links to specifications persist appropriately
Resolved in Pega Version 8.6.1
When linking Rules to Specifications, check-ins of some unrelated rules deleted the link. Investigation showed the deletion happened in the pzHandleLinksPostCheckIn activity, and was caused by an empty parameter page name that caused pcInsKey to not have a value, so all links returned by "Obj-Browse" were later deleted. To resolve this, an update has been made to insure the "Pass current parameter page" option in step 2 of the Connect REST PostCheckIn activity is enabled so that the downstream activity pzHandleLinksPostCheckIn behaves as expected.
INC-174296 · Issue 650753
Delayed JS/DF initialization failures will trigger alert
Resolved in Pega Version 8.6.1
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-174612 · Issue 659250
Queue Processor threads explicitly cleared before new interaction
Resolved in Pega Version 8.6.1
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-174694 · Issue 650779
Check added to ensure read locks are released
Resolved in Pega Version 8.6.1
Read locks were not being properly released if a thread was holding a read lock and the system encountered an issue such as an out of memory condition. To resolve this, an update has been made to DeclarativePageDefinitionCacheImpl which will check whether a thread holds any read lock before trying to acquire a write lock, and if so release all the read locks held by that thread.
INC-175205 · Issue 652530
Agent restart made more resilient
Resolved in Pega Version 8.6.1
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-175343 · Issue 655353
Invalid date handling added to Legacy Adapters
Resolved in Pega Version 8.6.1
Running the Job Scheduler activity failed with the error "not a valid date/time value". Investigation showed this was caused by LegacyPropertyAdapter.isEmpty being returned as true in case of properties having invalid values, and has been resolved by adding handling for an InvalidValueException in LegacyPropertyAdapter and LegacyPageAdapter.