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.
SR-D83424 · Issue 552722
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.
INC-120356 · Issue 560224
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.
SR-D84122 · Issue 547967
Added min INT comparison for BrowseByKeys
Resolved in Pega Version 8.5
Running the dataset with the Browse option worked as expected, but running it using BrowseByKeys operation and giving a negative value caused results to not be populated. To resolve this, a minimum INT value comparison has been added.
SR-D40785 · Issue 548939
WorkPageName preserved during passivation so attachments are correctly tracked
Resolved in Pega Version 8.5
When a work object was left open but inactive for a period, using the delete button in the pyAttachFieldRequired section caused the deletion of the Attachment Links for the 500 most recent attachments in the system with the same value for the AttachmentFieldName, regardless of which work object they were attached to. This was due to the delete attachments activity being executed with missing parameters: since data page loading was disabled and read-only data pages are not passivated, the value for the autopopulate property 'WorkPageName' was passed as empty. This has been resolved.
SR-D75053 · Issue 540913
Corrected Agent schedule time conversion
Resolved in Pega Version 8.5
After upgrade, a mismatch between the agent configuration and schedule was seen, causing an agent scheduled at 6PM Europe/London time to execute at 6AM Europe/London instead. Analysis of the Agent schedule rule showed that if the pyStartAmPm property was empty, the internal code miscalculated the AM_PM string as AM. That meant that if an agent was configured with 24 hour clock format and was set to run at 18:00 hrs, it executed at 6AM. The workaround for this issue involved resaving the agent, triggering the data transform pzSetStartAmPm to correct the field pyStartAmPm, but the issue has been corrected by adding handling for the pyStartAmPm == " corner case.