SR-D83424 · Issue 552724
Class Loader cache values wrapped with WeakReference for improved cleanup
Resolved in Pega Version 8.4.2
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-D87605 · Issue 547298
Indexes and tables updated to improve purge query performance
Resolved in Pega Version 8.4.2
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-D88813 · Issue 556090
Resolved getDatabaseIndices release
Resolved in Pega Version 8.4.2
While retrieving the indexes of the database, the result sets were not closed, leaving the cursors open as well. Eventually the number of open cursors exceeded the database max, preventing any further database operations. This has been resolved by appropriately releasing the cursors after finishing with them, preventing the failure.
SR-D89835 · Issue 554303
Updated padding character handling for access group hash
Resolved in Pega Version 8.4.2
While generating an access group hash from an access group name, Pega was using the '(' character as padding. However, Siteminder blocks the '(' character, causing requests to be rejected. To resolve this, the padding character will be removed while encoding and decoding will handle hashes both with and without the padding character.
SR-D91362 · Issue 556048
Updated handling for redirect location header
Resolved in Pega Version 8.4.2
After upgrade, browser refresh/reload was not working, instead displaying a grey screen with no error in Google Chrome and a 404 message in Microsoft Internet Explorer 11. Investigation showed this was due to a redirect request being sent without location header; this was caused by the pageToCopy thread being reused in the redirect even though it was null, resulting in the location header not being populated in the requestor page. To resolve this, the system has been updated to skip copying the pages and set then location header if the thread is the same.
SR-D91894 · Issue 557222
Class Loader cache values wrapped with WeakReference for improved cleanup
Resolved in Pega Version 8.4.2
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-D92054 · Issue 559068
Resolved passivation issues with Operator Preference records
Resolved in Pega Version 8.4.2
Blue screen errors were reported for several operators during Launch portal. This was traced to corruption of the BLOB during passivation, and has been resolved.
SR-D92635 · Issue 559221
API added to sync presence with requestor to clear inactive operator sessions
Resolved in Pega Version 8.4.2
An intermittent error message was seen indicating the maximum number of active sessions for the current operator had been reached even though there were not multiple logins and there was no requestor displayed in the requestor management landing page. This was traced to sessions that were not properly closed and cleared, and has been resolved by exposing an API that will sync the presence record with the requestor state so inactive sessions will be cleared.
SR-D93460 · Issue 558914
Transient property passivation handling improved
Resolved in Pega Version 8.4.2
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.
SR-D93560 · Issue 555447
Tomcat DBCP updated
Resolved in Pega Version 8.4.2
The tomcat-dbcp jar has been updated from 9.0.22 to 9.0.33 .