INC-131938 · Issue 598476
Locking and classmap improvements
Resolved in Pega Version 8.6
Threads were getting stuck inside classMap and tableInformationMap, causing nodes to go down. This was traced to issues with class map performance and locking, and has been resolved by replacing the lock library with a newer version and refactoring the tableInformationMapImpl class to use a concurrent hashmap instead.
INC-132059 · Issue 597305
Enhancement added to fix corrupted operators
Resolved in Pega Version 8.6
After upgrade, an issues were seen with older operator IDs: it was not able to save the operator ID, switching the portal to admin studio was not working correctly, and it was not possible to launch the case manager portal with the migrated operator IDs. The issues were not seen with operators created after the upgrade. This was traced to corruption in the BLOB, and has been resolved by adding an enhancement to run a utility that will fix the existing corrupted operators.
INC-132088 · Issue 603085
Updated Tracer for cluster events
Resolved in Pega Version 8.6
When running the tracer from the Admin Studio Listener management landing page, Tracer was always fetching data from one node only even though events were generated on another node. This was due to the specific node where the Listener was running being passed to the concern activity while launching the tracer; the Tracer Client node did not have data to check if the event was being populated on another node, and the result was to always fetch data from one node only even though events were generated on another node. To resolve this, the web node ID where the event is running will be passed.
INC-132658 · Issue 590951
Atmosphere updated to resolve request object recycle exception
Resolved in Pega Version 8.6
The exception "java.lang.IllegalStateException: The request object has been recycled and is no longer associated with this facade" was traced to a request object being recycled in Tomcat because of pooling. To resolve this, a fix was made in the Atmosphere open source library to ignore such exceptions. A new jar with version 2.4.5.8 has been uploaded to the repository and defaultVersionsByGradle has been updated with this version.
INC-134143 · Issue 594198
Export URL encryption update for BAC
Resolved in Pega Version 8.6
After applying URL Encryption and URL obfuscation DSS changes, the export option was not working from data types. This was traced to the URL being decrypted as part of the standard handling: If BAC is turned on, it accepts only encrypted URLs. To resolve this, an update has been made to ensure the URL remains encrypted in the declare expression when appropriate.
INC-134260 · Issue 588366
Tomcat-dbcp upgrade
Resolved in Pega Version 8.6
Tomcat-dbcp has been upgraded to version 9.0.37 .
INC-135065 · Issue 598716
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-135313 · Issue 596097
Correct circumstanced version of portal loads
Resolved in Pega Version 8.6
Desktop users were seeing the mobile circumstanced version on the application portal immediately upon login. This was a missed use case for a user logging into a mobile portal first and then into a desktop, caused by data between the two sessions being shared in an invalid way. This has been resolved by updating the save work in progress feature to prevent UI data from being shared between mobile and desktop.
INC-135359 · Issue 587039
CORS header configuration added for Stream tier
Resolved in Pega Version 8.6
An enhancement has been added that allows setting the CORS header (Access-Control-Allow-Origin) to allow *.DOMAIN.com on Stream tier (/stream/view & /stream/click) calls by way of the setting /stream/httpHeaders .
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.