SR-D85839 · Issue 550938
Support added for custom Kafka connection properties
Resolved in Pega Version 8.5
An enhancement has been added to allow specifying custom Kafka connection properties in the Data-Admin-Kafka data instance to allow connections to external Kafka through the common client configs, ssl configs, and sasl configs.
SR-D90505 · Issue 550990
Repaired Tracer use with Google Chrome
Resolved in Pega Version 8.5
After running Tracer while using Chrome, closing it and trying to run another resulted in an error indicating "Cannot Launch multiple tracer sessions for a requestor". This was identified as a bug with Google Chrome Versions greater than 70 and was caused by Chrome deprecating the use of sync XHR on page dismissal, and has been resolved by modifying the system to use a beacon API instead.
INC-126091 · Issue 561825
Repaired Tracer use with Google Chrome
Resolved in Pega Version 8.5
After running Tracer while using Chrome, closing it and trying to run another resulted in an error indicating "Cannot Launch multiple tracer sessions for a requestor". This was identified as a bug with Google Chrome Versions greater than 70 and was caused by Chrome deprecating the use of sync XHR on page dismissal, and has been resolved by modifying the system to use a beacon API instead.
SR-D94258 · Issue 560795
Thread context updated to supply steppage
Resolved in Pega Version 8.5
After upgrade, Server Startup was failing with the error "PEGA Rules Server not available". Investigation traced this to missing steppage information while invoking Rule-Utility-Function (from declare trigger when rule) during startup, which was caused by the thread calling the declare trigger, which was different from the thread running WhenRule, not being properly initialized during startup. To resolve this, the thread context has been changed to gThread, which contains the necessary steppage information.
INC-126662 · Issue 561314
Thread context updated to supply steppage
Resolved in Pega Version 8.5
After upgrade, Server Startup was failing with the error "PEGA Rules Server not available". Investigation traced this to missing steppage information while invoking Rule-Utility-Function (from declare trigger when rule) during startup, which was caused by the thread calling the declare trigger, which was different from the thread running WhenRule, not being properly initialized during startup. To resolve this, the thread context has been changed to gThread, which contains the necessary steppage information.
SR-D74921 · Issue 551788
Error condition will close WebSocket connection
Resolved in Pega Version 8.5
An async listener has been added that will close the WebSocket connection when an error condition is encountered.
SR-D71145 · Issue 536369
PropertySet will iterate over changeList map copy to resolve CME
Resolved in Pega Version 8.5
An empty menu was seen intermittently when handling incoming email, and a ConcurrentModificationException error was logged. Investigation showed that a step scope changeList map used in the handleChaining method was sometimes modified by another process while the first one was iterating over it. To resolve this, PropertySet will receive copies of the change list map from clipboard pages instead of the original map.
SR-D87605 · Issue 547297
Indexes and tables updated to improve purge query performance
Resolved in Pega Version 8.5
Due to work done previously, purge queries to clean up the application ruleset index and application hierarchy_flat tables were running slowly or not returning the expected results. This has been resolved.
SR-D84876 · Issue 547690
Performance improvement for Oracle 12c queries
Resolved in Pega Version 8.5
In order to compensate for a known issue with Oracle 12c that can cause repeated queries at certain times to cause database contention, Oracle pre/post processing steps have been added to improve performance in this environment.
SR-D91894 · Issue 557221
Class Loader cache values wrapped with WeakReference for improved cleanup
Resolved in Pega Version 8.5
Out Of Memory exceptions due to Metaspace were observed on Web tier instances running with a max Metaspace size of 2GB. Investigation showed that in PRClassLoaderDB, mLoaderCache values were wrapped with a SoftReference. To resolve this, the Class Loader cache values will be wrapped with a WeakReference, allowing the cache to free memory when it is no longer needed. JVM options has also been added to switch types of References being used if there is a preference.