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 .
SR-D94258 · Issue 560796
Thread context updated to supply steppage
Resolved in Pega Version 8.4.2
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-D94689 · Issue 555423
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-D95074 · Issue 566433
Updated logging to avoid unnecessary errors
Resolved in Pega Version 8.4.2
Errors were seen in the Pega rules log when a service case was launched from an email interaction case. This has been resolved by updating the system to avoid error logging for a configuration not supported for declaratives, such as named page references in 'when' rules.
SR-D95353 · Issue 557043
Null check and enhanced logging added to Update Existing Application
Resolved in Pega Version 8.4.2
While performing "Update Existing Application" step as part of post upgrade activities, errors were seen about hidden or circumstanced rules relating to "prprivate-exec.jar:?". Investigation indicated that rulesets were being iterated and compared, but it was not clear which ruleset might be causing the issue. The root cause was code that used an integer type in the comparison, leading to a null pointer error when it was null. To resolve this, a check has been added that will assign a value of 0 if the value is null in the comparison, and infoForced logging will be used to tell what caused the null.
SR-D95396 · Issue 556878
Enhancements added for Auto Populate diagnostics
Resolved in Pega Version 8.4.2
Diagnostics and tracer events have been added for AP copy operation to allow more visibility into code during AP copy issues in future: stack trace for all AP tracer events, diagnostic logs for auto populate behavior during copy, and added code to turn on AP logging during copy.
SR-D95495 · Issue 561465
Revised query to resolve VTable initialization error
Resolved in Pega Version 8.4.2
While running an import in a multi-tenant environment, latency and VTable initialization exceptions were seen. This has been resolved by updating the query with a JOIN clause when the SQL query is being built that will allow the import process to run without causing any issues.
SR-D95511 · Issue 557292
Decision table testConsistency updated to include duplicate columns
Resolved in Pega Version 8.4.2
Show Conflicts incorrectly reported unreachable conditions for a decision table and there was a red severe warning ribbon on the top of the rule after saving when in actuality the conditions were unique and the execution was correct, with the runtime execution of each row in the table giving the correct results. This was traced to the use of a property as the column header for multiple columns: testConsistency marked the columns other than the first as duplicates and excluded them from the consistency check. As a result, when a decision table had 3+ rows with a value in the first row and empty values for the rest of the rows and used an operator such as >, all rows starting with the 3rd row became unreachable because the first row covered values > 1 and the second covered the rest, therefore the third was unreachable. To resolve this, the system has been updated to involve all duplicate columns in the consistency check.