SR-D44834 · Issue 513641
Concurrent session count updated to avoid false blocks
Resolved in Pega Version 8.4
In multiple scenarios, Operators intermittently received the error "The current session is blocked, as the maximum number of active sessions for the current operator has been reached." Investigation showed that in some cases after the browser is closed and reconnected, there were parallel requests going to the server. While one request was updating a flag in requestor object after the Presence record (Cluster) was updated, the other request was checking the Concurrent session count. Because request 1 had already updated the record in Presence, the system noted the count check as an active session: to correct this, the system has been updated so the current session is excluded from the max sessions reached check.
SR-D4641 · Issue 501790
Max node discovery timeout configuration added
Resolved in Pega Version 8.4
When nodes were restarted, a few of the nodes formed a different cluster instead of joining the existing cluster. This was traced to slow start-ups timing out when Hazelcast was trying to cluster. An enhancement has now been added to allow local configuration for max node timeout on discovery.
SR-D46536 · Issue 515794
Custom agent next run time will be rescheduled if the run failed
Resolved in Pega Version 8.4
If a customized agent that was set to run every day encountered an exception and failed to run, restarting the agent did not update it to the next run time; it still returned the passed trigger time as its next execution time. This has been resolved with an update that will reschedule the run if the next run time is in the past.
SR-D48396 · Issue 520425
Hazelcast upgraded to resolve node startup issue
Resolved in Pega Version 8.4
Post data upgrade, the ADM tier failed to start and the error "java.lang.IllegalStateException: Node failed to start!" appeared. This was traced to a dormant bug in Hazelcast 3.11 that caused starting nodes to fail when the Hazelcast master node was shutting down, which was exposed by recent Pega changes made to enable parallel restarts of nodes in Cloud environments. Hazelcast delivered a fix for the parallel restart problem and the hotfixed jar has been merged into the platform. In addition, previous logic for loading Admin Studio waited 30 seconds before timing out when fetching information for each node. This caused issues with large clusters and Admin Studio not loading. The logic has been updated in the Admin Studio UI to load the page despite delays/issues waiting for nodes to respond to the gathering of cluster data, and the algorithm to detect remote-call timeout has been updated and is applicable to batch operation.
SR-D50471 · Issue 517260
Requestor information restricted to improve security
Resolved in Pega Version 8.4
An intermittent issue was seen where User1 would log in and User2 would then log in and see the data/profile of User1. This was traced to an exception in the session logic which prevented the previous requestor ID from being cleared, causing it to then be mapped to the second user. To correct this, WebStandardImpl has been updated to restrict the requestor information in the session object and in the HTTP API while retrieving the requestor.
SR-D51554 · Issue 514063
Local UUID cache will be updated when merge event is detected
Resolved in Pega Version 8.4
Cluster-related issues were seen in multiple production clusters. For some nodes in the cluster the Cluster Management screen showed all expected nodes with valid Node IDs displayed, and on other nodes the Cluster Management screen showed the node ID of itself, SERVER@localhost:5701. On an impacted node displaying the wrong ID, the Node Information landing page did not work and displayed the error "Unable to execute job on ." Multiple advanced agents running on nodes in the affected clusters, both with correct and incorrect IDs, also failed with a similar error "Unable to execute job on <node's job id>". This was traced to a merge performed after a split brain. To resolve this, the code has been updated to handle merge events: when the node UUID is changed as part of a split brain recovery, the local UUID cache will be updated when the merge event is detected.
SR-D52336 · Issue 518388
Local UUID cache will be updated when merge event is detected
Resolved in Pega Version 8.4
Cluster-related issues were seen in multiple production clusters. For some nodes in the cluster the Cluster Management screen showed all expected nodes with valid Node IDs displayed, and on other nodes the Cluster Management screen showed the node ID of itself, SERVER@localhost:5701. On an impacted node displaying the wrong ID, the Node Information landing page did not work and displayed the error "Unable to execute job on ." Multiple advanced agents running on nodes in the affected clusters, both with correct and incorrect IDs, also failed with a similar error "Unable to execute job on <node's job id>". This was traced to a merge performed after a split brain. To resolve this, the code has been updated to handle merge events: when the node UUID is changed as part of a split brain recovery, the local UUID cache will be updated when the merge event is detected.
SR-D52785 · Issue 518410
XSS protection added to layout runtime java and whitelist validation available for host/XFHost
Resolved in Pega Version 8.4
In order to protect against XSS issues, filtering has been added to the RepeatDynamicIndex parameter value in layout runtime java. In addition, a validation for X-Forward-Host value has been added which will be read from a local configuration. This is in the form of a white list regex filter for the host/XFHost header to ensure the URL's actions cannot be redirected.
SR-D54319 · Issue 532529
API added to sync presence with requestor to clear inactive operator sessions
Resolved in Pega Version 8.4
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-D54628 · Issue 524568
jFreeChart upgraded
Resolved in Pega Version 8.4
Chart generation activities have been updated to use JFreeChart v1.0.19.