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.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-146030 · Issue 602605

Added queue process tracer cleanup on node restart

Resolved in Pega Version 8.3.5

If a node restart occurred while a queue process trace was in progress, some entries in the tracer distributed map were not cleared properly and a subsequent tracer failure was encountered indicating a current trace by a requestor on same operator Id was already running. This has been resolved by clearing the tracer distributed map on node startup for stale entries associated with this node.

INC-139802 · Issue 594033

Extra logging and more resiliency for cleanup daemons

Resolved in Pega Version 8.3.5

Null pointer exceptions thrown by daemon threads that clean requestors and handle agent changes can result in a high number inactive requestors. Additional logging has been out into place to help capture information to identify the offending data, and master daemons for requestors and for new agents have been made more resilient to any Null pointer exception thrown by the diagnostics code so they do not stop their work.

INC-142629 · Issue 594555

Resolved alert from disabled job scheduler

Resolved in Pega Version 8.3.5

An urgent event alert was seen for scheduler which was disabled in production. This was traced to null pointer exceptions originating in the JobSchedulerLifeCycleManagerImpl call, and has been resolved by fixing a potential null dereference. Additional logging has also been introduced.

INC-122112 · Issue 599794

Updated SLA table clearance

Resolved in Pega Version 8.3.5

After cases were resolved, SLA entries were not getting cleared from the SLA table. This caused the SLA table to have a huge number of Overall SLA and PendFlow details present for cases that were resolved or moved to the next state, which impacted case processing via SLA Agent. This was traced to SLA queue-items not being removed by delete-deferred as expected, and has been resolved by invalidating the deferred operations and scheduling item removal.

INC-136817 · Issue 596489

Added database query optimization and cache invalidation logging

Resolved in Pega Version 8.3.5

Web nodes were going down during deployment due to failed health checks. This was traced to queries firing even when there was no rule change, and was due to unnecessary cache invalidations. An update has been made which will optimize and analyze declarative database queries and capture diagnostic details on any invalidation of the declarative reference information cache.

INC-135065 · Issue 598718

Added database query optimization and cache invalidation logging

Resolved in Pega Version 8.3.5

Web nodes were going down during deployment due to failed health checks. This was traced to queries firing even when there was no rule change, and was due to unnecessary cache invalidations. An update has been made which will optimize and analyze declarative database queries and capture diagnostic details on any invalidation of the declarative reference information cache.

INC-122072 · Issue 581030

Delay in writing database template records resolved

Resolved in Pega Version 8.3.5

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-138253 · Issue 597571

Handling added to ensure proper Data-Admin-DB-Table name records

Resolved in Pega Version 8.3.5

As part of property optimization, After exposing the property "SolutionName" using the wizard, the value was not visible in a new column for existing records after the completion of the column population job. This was traced to an issue with DBSchemaDDLExecutor expecting lowercase Data-Admin-DB-Table names, and the wizard has been updated to ensure Data-Admin-DB-Table name records are all lowercase.

INC-125972 · Issue 604082

Improved resolved rules cache

Resolved in Pega Version 8.3.5

When Rule resolution iterated over a candidate list to fetch a candidate, performance issues were seen on very large sites. To resolve this, an enhancement has been added that will cache the resolved virtual table entries to optimize performance in high demand use cases like DSM.

INC-131938 · Issue 598478

Locking and classmap improvements

Resolved in Pega Version 8.3.5

Threads were getting stuck inside classMap and tableInformationMap, causing nodes to go down. This was traced to issues with classmap performance and locking, and has been resolved by replacing the lock library with a newer version and refactoring the tableInformationMapImpl class to use a concurrent hashmap instead.

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