INC-128899 · Issue 586972
Resolved BIX Extract Summary Status Count mismatch
Resolved in Pega Version 8.6
A mismatch was seen between the summary of the Extract Summary Status Count in the Execution History stats versus the logs, for example the execution history saying 98.74% completed while the log says 100% or 100.45% completed. Investigation showed there was mismatch in the query based on the filter value given in the extract rule and the where clause in the query that resulted in an error in calculating percentage in case of any exception. This has been resolved.
INC-130176 · Issue 585373
Removing Page List removes all cached pages
Resolved in Pega Version 8.6
A previous change was made such that when removing a Page List property, its size is removed from the size-specific cache as well. A further enhancement has been made so that when a Page List is removed, the system will clear the pageCache of all cached pages in the Page List.
INC-130886 · Issue 590375
Bad Stream error after passivation resolved
Resolved in Pega Version 8.6
A "Bad Stream" error was seen when attempting to reassign a case to the Workbasket, and a save of the work object failed. This was caused by a corruption of the work object during passivation, and has been resolved.
INC-131635 · Issue 579854
New troubleshooting guide for exceptions on Stream nodes
Resolved in Pega Version 8.6
A new troubleshooting topic has been added to the documentation for decision nodes which will assist with resolving Stream node exceptions.
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 .