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.

INC-134315 · Issue 578366

Resolved 400 error on second browser session

Resolved in Pega Version 8.5.1

When accessing application URLs in two tabs of a browser window, logging into the second session was throwing a 400 invalid request. This has been resolved by adding specified activities to an allow list which will bypass URLObfuscation in un-authenticated mode. Non-listed activities will be processed using URLObfuscation if it is enabled.

INC-139611 · Issue 587599

Timezone.getDefault function replaced for performance improvement

Resolved in Pega Version 8.5.1

Blocking threads were seen around the GregorianCalendarFactory.clearObject(Object) function, leading to an adverse impact on the performance. TimeZone.getDefault() is a synchronized method call, and under high load this method caused contention when more date-related APIs were invoked. To resolve this, Timezone.getDefault() has been removed and the function has been assigned to a static variable used in the clearObject() API.

SR-D97738 · Issue 580162

Class Loader cache values wrapped with WeakReference for improved cleanup

Resolved in Pega Version 8.5.1

Out Of Memory exceptions due to Metaspace were observed on Web tier instances running with a max Metaspace size of 2GB. Investigation showed that in PRClassLoaderDB, mLoaderCache values were wrapped with a SoftReference. To resolve this, the Class Loader cache values will be wrapped with a WeakReference, allowing the cache to free memory when it is no longer needed. JVM options has also been added to switch types of References being used if there is a preference.

INC-122072 · Issue 581029

Delay in writing database template records resolved

Resolved in Pega Version 8.5.1

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-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-135849 · Issue 582939

Encrypted SOAP response token generation updated

Resolved in Pega Version 8.5.1

After configuring a SOAP service that used signature and encryption on the response, the response being created was incorrect and could not be decrypted by the receiver. Investigation showed that the API used to generate the SOAP headers was not setting the wsse11:TokenType element, causing receivers which enforce BSP compliance to fail. This has been resolved by modifying the custom webservices-rt-pega2 jar to set the token type in the case of a response encryption policy.

INC-136019 · Issue 584808

EmailListener restart correctly reflects Inbox folder change

Resolved in Pega Version 8.5.1

The Email Listener did not pick up a change in the INBOX folder name when the listener was restarted, but did when the server itself was restarted. This was due to the folder name being cached but not being included in the cache key: a cache change only occurs when the key of the cache changes. This meant that even after changing the folder name, the object was treated as 'not changed' and returned the older connection with older folderName. This has been resolved by adding the foldername to the cache key.

INC-130176 · Issue 585372

Removing PageList removes all cached pages

Resolved in Pega Version 8.5.1

A previous change was made such that when removing a pageList property, its size is removed from the size-specific cache as well. A further enhancement has been made so that when a PageList is removed, the system will clear the pageCache of all cached pages in the PageList.

INC-138649 · Issue 585356

Timezone retrieval performance enhancement

Resolved in Pega Version 8.5.1

In order to improve performance and reduce a potential bottleneck for concurrent threads, PRDateTimeUtilsImpl has been updated to use a common GMT timezone object rather than getting the timezone for each operation for each function call.

INC-140750 · Issue 589925

Resolved post-passivation login issue

Resolved in Pega Version 8.5.1

An authentication error was seen when operators tried to log in again after passivation. This was traced to a corrupted BLOB, and has been resolved.

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