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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-D77316 · Issue 539260

Resolved thread deadlock for rules upgrade process

Resolved in Pega Version 8.2.6

Platform upgrade was getting hung during the rules upgrade process. This was traced to a deadlock related to the conclusion cache entry for a property needing to make a call to declarative cache, where it tried to hold a read-write lock on a resource that was already locked by another thread. This has been resolved by replacing lock with tryLock to avoid deadlock.

SR-D78531 · Issue 542000

Encoding added for special characters in JFROG filenames

Resolved in Pega Version 8.2.6

A blank screen or the error "Unable to get the file from Repository" appeared when attempting to attach a file from JFROG Repository if the file name contained special characters. This has been resolved by modifying the artificatory URL generation to properly encode special characters during file download.

SR-D80668 · Issue 543867

Performance improvement for queries on Kafka partitions

Resolved in Pega Version 8.2.6

Even though there were multiple dataflow nodes available in the cluster, all requests were going to single node and causing system slowness. Investigation showed there was a queue processor rule that included the pxPartitionKey attribute which forced all records to be sent to a single partition by Kafka producers. This attribute has been removed.

SR-D89304 · Issue 519812

ClusterAndDBCleaner repaired

Resolved in Pega Version 8.2.6

An error in the logic order of events caused a compilation error for pyClusterAndDBCleaner, leading to old records created by the system/node utilities to not be automatically removed as expected. This has been corrected.

SR-D53835 · Issue 524214

Handling added for custom authentication in embedded mashup

Resolved in Pega Version 8.4.1

After embedding the Mashup gadget in an external application, at browser refresh a Cross-Origin Read Blocking (CORB) warning appeared and the gadget did not load as expected. A second refresh cleared the error. Investigation showed that when custom authentication is configured, 'use SSL' is checked in Authentication service. That meant that when the user was authenticated, the redirection was not considering the query string entered before authentication and the CORB warning was issued due to a change in response. Because there is special handling for the above use case and post-authentication redirection does not happen through the normal flow (HttpAPI), this issue has been resolved by honoring the query string stored in requestor (entered by user) while redirecting.

SR-D60284 · Issue 550560

Delete Requestor method updated for use with CMT

Resolved in Pega Version 8.4.1

JMS MDB Listeners with Container Managed Transaction (CMT) enabled in Websphere 8.5 had global transactions fail. To initialize a JMS-MDB listener, a requestor of type APP is used. Upon the service being fully initialized, the requestor is removed by executing a delete operation followed by a COMMIT. However, in this scenario, the initialization operation is running within a CMT context and a SQLException was raised indicating that the commit was not allowed. To resolve this, the delete requestor method has been refactored to take into account the CMT context so the commit is not executed if the transaction is managed by the container.

SR-D60830 · Issue 533031

Logic update for classloading synchronization

Resolved in Pega Version 8.4.1

The synchronization logic for classloading has been updated to resolve intermittent deadlocking seen when two DataFlow threads are executing a distribution test.

SR-D62490 · Issue 527292

Application/CSV type explicitly included to assist Android Chrome

Resolved in Pega Version 8.4.1

Android Chrome was unable to recognize a CSV file under content-type="application/*" , resulting in the download being rejected. To resolve this, "application/csv" will be explicitly included in the request content type when appropriate.

SR-D64083 · Issue 542887

Compilation logic error corrected

Resolved in Pega Version 8.4.1

A compilation failure on upgraded systems using the JDK 11 compilation of libraries that include Pega 7 functions that have INCLUDE statements that are not supported in JDK 11 was traced to a logic error added when enhancing debug logging. This has been corrected.

SR-D64608 · Issue 544389

Corrected filedownload extension header issue

Resolved in Pega Version 8.4.1

Filedownload header contained plain non-ascii characters which caused a security violation issue. This has been resolved by removing the filedownload header from the HTTP response when the sendfile API is used with inputstream to download a file.

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