INC-135821 · Issue 588999
Timeout for node to join cluster increased and made configurable
Resolved in Pega Version 8.6
Hazelcast timeouts were causing application restart failures. This was traced to a rare case scenario of heavy processing on the primary node causing the new node to not be able to join the cluster within the designated 5 minute threshold. To compensate for this, the default time to join has been increased to 9 minutes and a prconfig setting has been added to configure the time setting.
INC-135823 · Issue 586418
Transient property passivation handling improved
Resolved in Pega Version 8.6
Frequent "com.pega.pegarules.pub.PRRuntimeException" errors were seen in the production log file while working on the WO. This was traced to corruption in the blob caused by transient properties during passivation. To resolve this, corrections have been made to the handling for the transient property entries in the blob. In addition, a utility has been provided to restore existing corrupted operators.
INC-136019 · Issue 584809
EmailListener restart correctly reflects Inbox folder change
Resolved in Pega Version 8.6
The Email Listener did not pick up a change in the INBOX folder name when the listener was restarted, but did when the server itself was restarted. This was due to the folder name being cached but not being included in the cache key: a cache change only occurs when the key of the cache changes. This meant that even after changing the folder name, the object was treated as 'not changed' and returned the older connection with older folderName. This has been resolved by adding the foldername to the cache key.
INC-136708 · Issue 584868
Query String Parameter handling updated for REST service
Resolved in Pega Version 8.6
Technical parameters starting with underscore, such as _pageNum, _pageSize, and _last_modified that were used as Query String Parameters in a Service-REST caused it to fail with the error "failed:Inbound data mapping failed". This was caused by the system considering the parameter names as invalid. To resolve this, the design time and validation handling has been updated for the query string parameter.
INC-136817 · Issue 596488
Added database query optimization and cache invalidation logging
Resolved in Pega Version 8.6
Web nodes were going down during deployment due to failed health checks. This was traced to queries firing even when there was no rule change, and was due to unnecessary cache invalidations. An update has been made which will optimize and analyze declarative database queries and capture diagnostic details on any invalidation of the declarative reference information cache.
INC-137235 · Issue 586080
Validations and rules tuning
Resolved in Pega Version 8.6
Issues relating to an extra row being added to auto-populated properties, adding a 'when' visibility to a picklist property, and errors saving nested properties have been resolved, and performance of the overall system has been improved.
INC-137882 · Issue 599137
Hazelcast will be used to determine node presence
Resolved in Pega Version 8.6
When calling logoff from the end user portal, sporadic PresenceStandardLifeCycleListener exceptions were seen during high load periods. This was traced to changes made in the Service Discovery behavior: when there is an issue with the node and heartbeats are missed, the node goes to Safe Mode. This caused the topology to change and trigger clearing off presence sessions, but the node still received service requests and this issue was seen. To resolve this, an updated has been made so the system will rely on the Hazelcast listener instead of service discovery to determine whether a node has left.
INC-138041 · Issue 590556
Handling added to ensure proper Data-Admin-DB-Table name records
Resolved in Pega Version 8.6
As part of property optimization, after exposing the property "SolutionName" using the wizard, the value was not visible in a new column for existing records after the completion of the column population job. This was traced to an issue with DBSchemaDDLExecutor expecting lowercase Data-Admin-DB-Table names, and the wizard has been updated to ensure Data-Admin-DB-Table name records are all lowercase.
INC-138243 · Issue 584898
Performance improvement in When parsing
Resolved in Pega Version 8.6
After upgrade, performance issues were seen in the execution of rules with When conditions. This has been resolved by modifying the code to address some inefficiencies in the parsing method.
INC-138253 · Issue 597570
Handling added to ensure proper Data-Admin-DB-Table name records
Resolved in Pega Version 8.6
As part of property optimization, after exposing the property "SolutionName" using the wizard, the value was not visible in a new column for existing records after the completion of the column population job. This was traced to an issue with DBSchemaDDLExecutor expecting lowercase Data-Admin-DB-Table names, and the wizard has been updated to ensure Data-Admin-DB-Table name records are all lowercase.