Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

INC-134932 · Issue 578545

Timeout for node to join cluster increased and made configurable

Resolved in Pega Version 8.4.3

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-125122 · Issue 581254

JMX authentication added

Resolved in Pega Version 8.4.3

Support has been added for JMX authentication through user and password.

INC-134069 · Issue 583022

Added Kafka logging

Resolved in Pega Version 8.4.3

In order to help diagnose issues encountered during Kafka background processing, additional logging has been added to QueueProcessorDatasetHandler.

INC-135359 · Issue 587037

CORS header configuration added for Stream tier

Resolved in Pega Version 8.4.3

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-139619 · Issue 597332

Agent tracing handling updated

Resolved in Pega Version 8.4.3

When attempting to trace agents the error "Unable to trace the agent" appeared on screen. Investigation showed that the data page used by the Tracer was not always available in a thread that was displaying the section, most commonly if the section was using deferred loading. This has been resolved by using a data page available in a thread that opens a Tracer's section.

INC-140879 · Issue 596569

Agent tracing handling updated

Resolved in Pega Version 8.4.3

When attempting to trace agents the error "Unable to trace the agent" appeared on screen. Investigation showed that the data page used by the Tracer was not always available in a thread that was displaying the section, most commonly if the section was using deferred loading. This has been resolved by using a data page available in a thread that opens a Tracer's section.

INC-142792 · Issue 594500

Modified thread data page cleanup

Resolved in Pega Version 8.4.3

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-118760 · Issue 580172

Atmosphere updated to resolve request object recycle exception

Resolved in Pega Version 8.4.3

The exception "java.lang.IllegalStateException: The request object has been recycled and is no longer associated with this facade" was traced to a request object being recycled in Tomcat because of pooling. To resolve this, a fix was made in the Atmosphere open source library to ignore such exceptions. A new jar with version 2.4.5.8 has been uploaded to the repository and defaultVersionsByGradle has been updated with this version.

INC-122072 · Issue 581028

Delay in writing database template records resolved

Resolved in Pega Version 8.4.3

After upgrade. a real-time event based campaign with an offer flow that used a database template showed an excessive delay in updating the database template. A queue entry related to "WriteOutboundAgent" was also showing as failed, and analysis of the logs showed that the transaction type was not being set. This was traced an exception during a regular close operation of the result set iterator: the API used to close the transaction contained code specific to PostgreSQL while the site was using Oracle. This has now been resolved.

INC-130055 · Issue 578632

Page Validation logging updated

Resolved in Pega Version 8.4.3

In order to enhance troubleshooting, additional logging has been added to capture information for Page Validation failures.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us