SR-D96836 · Issue 555750
Refinements made to MarkerNode memory use
Resolved in Pega Version 8.4.2
Significant memory usage can be observed when data join in strategies are missing the join conditions. E.g., when the primary source in the strategy can have up to 300 or even more propositions, the join without the join condition would perform a cartesian product with possibly up to 400 or even more records returned. This may cause performance degradation. To guard against this, an update has been made that seeks to prevent repetitive markers being accumulated under a MarkerNode while trying not to rely on any implementation of equality and hashCode for individual marker implementations.
SR-D96847 · Issue 556988
Unneeded MBean startup warning removed
Resolved in Pega Version 8.4.2
After upgrade, Catalina logs indicated the error "WARN com.pega.dsm.dnode.api.prpc.service.monitoring.MBeanDSMService - Service DataFlow doesn't implement Monitoring operation". This was due to a flaw in the way the data flow DSM service was initialized in client mode. The exception itself was not a problem and did not impact functionality, but the client initialization has been modified to remove the warning.
INC-126556 · Issue 564032
Declaratives disabled during startup
Resolved in Pega Version 8.4.2
Declaratives firing before the engine is fully up can lead to null pointer errors. In order to avoid this condition, declaratives will be disabled during startup so that unnecessary operations can be avoided and system can be started faster.
INC-134932 · Issue 578544
Timeout for node to join cluster increased and made configurable
Resolved in Pega Version 8.5.1
Hazelcast timeouts were causing application restart failures. This was traced to a rare case scenario of heavy processing on the primary node causing the new node to not be able to join the cluster within the designated 5 minute threshold. To compensate for this, the default time to join has been increased to 9 minutes and a prconfig setting has been added to configure the time setting.
INC-133270 · Issue 581839
Automatic agent restart added for temporary connection issues
Resolved in Pega Version 8.5.1
An agent that was stopped due to an issue with the database connection did not recover when the connection was reestablished. To resolve this, updates have been made that will handle an automatic restart of the agents when there are temporary connection issues.
INC-135359 · Issue 587038
CORS header configuration added for Stream tier
Resolved in Pega Version 8.5.1
An enhancement has been added that allows setting the CORS header (Access-Control-Allow-Origin) to allow *.DOMAIN.com on Stream tier (/stream/view & /stream/click) calls by way of the setting /stream/httpHeaders .
INC-134069 · Issue 583024
Added Kafka logging
Resolved in Pega Version 8.5.1
In order to help diagnose issues encountered during Kafka background processing, additional logging has been added to QueueProcessorDatasetHandler.
INC-142792 · Issue 594499
Modified thread data page cleanup
Resolved in Pega Version 8.5.1
Some cases were becoming stuck at a particular stage and not proceeding further even though the task in the backend was complete. Investigation traced this to work done that removed declarative pages at the thread level to optimize performance while other clipboard pages were retained, and the issue has been resolved by deleting all thread data pages after every item processed by the agent.
INC-125122 · Issue 581255
JMX authentication added
Resolved in Pega Version 8.5.1
Support has been added for JMX authentication through user and password.
INC-130886 · Issue 590374
Bad Stream error after passivation resolved
Resolved in Pega Version 8.5.1
A "Bad Stream" error was seen when attempting to reassign a case to the Workbasket, and a save of the work object failed. This was caused by a corruption of the work object during passivation, and has been resolved.