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-217904 · Issue 730432

New prconfigs added to handle lob closed error

Resolved in Pega Version 8.8

BIX extraction was encountering the SQL error "Invalid operation: Lob is closed" while reading the BLOB, but the rest of the records were able to be extracted. This was traced to previous work done to resolve an issue where Oracle temporary space used to write the LOB was not freed up after writing records to Log-Service-File when using OJDBC8 or OJDBC10 versions. This change caused an issue for DB2 where the freed BLOB was still trying to be extracted. To address this, new prconfig settings have been introduced to control freeing BLOB memory. If the error is seen regarding the lob being closed, add and disable these settings (set value as false) in the pronfig.xml file. DATABASE_MANAGEMENT_FREELOB: settingName: database/management/freeLOB description: If this flag is set to false, it controls the free memory calls defaultValue: true DATABASE_MANAGEMENT_FREEPAGEDBMAPPERLOB: settingName: database/management/freePageDBMapperLOB description: If this flag is set to false, it controls the free memory calls. defaultValue: true Following this change, restart the server.

INC-218234 · Issue 734687

DSS added to skip 'Has Purge Happened Since Startup'

Resolved in Pega Version 8.8

The Purge Agent did not finish execution, exiting with the error "skipping purge because HasPurgeHappenedSinceStartup == false". This was traced to the local site policy of restarting their nodes every week, which was not aligned with the system default purge policy. To address this, a new DSS "skipHasPurgeHappenedSinceStartupCheck" has been added to the Pega-RulesEngine ruleset. When set to true, the check for 'Has Purge Happened Since Startup' will be skipped.

INC-218463 · Issue 726502

Common TransformerFactory method added for greater compatibility

Resolved in Pega Version 8.8

In Service-SOAP, mapping request headers and parameters to the clipboard (instead of mapping to a Parse XML rule) resulted in blank values on the primary page of the service activity when using the IBM WebSphere Liberty app server. In this case, instantiating the JAXP TransformerFactory object using the com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl parameter resulted in a transformer that serialized the XML to an empty string instead of the correct XML. To resolve this, an update has been made to make a common TransformerFactory method to ensure IBM JDK in WAS deployments function as expected.

INC-218532 · Issue 742524

File listener error recovery resumes from failure point

Resolved in Pega Version 8.8

When file listeners were unable to parse a file due to exception, the automatic error recovery did not start parsing from the correct location. Investigation showed the segment was not tracked during file listener run, so during error recovery the file listener always started processing from the first segment instead of the segment from which it failed. This was a missed use case and has been resolved by tracking the active segment and utilizing it during the error recovery run of the file listener.

INC-218802 · Issue 736911

New prconfigs added to handle lob closed error

Resolved in Pega Version 8.8

BIX extraction was encountering the SQL error "Invalid operation: Lob is closed" while reading the BLOB, but the rest of the records were able to be extracted. This was traced to previous work done to resolve an issue where Oracle temporary space used to write the LOB was not freed up after writing records to Log-Service-File when using OJDBC8 or OJDBC10 versions. This change caused an issue for DB2 where the freed BLOB was still trying to be extracted. To address this, new prconfig settings have been introduced to control freeing BLOB memory. If the error is seen regarding the lob being closed, add and disable these settings (set value as false) in the pronfig.xml file. DATABASE_MANAGEMENT_FREELOB: settingName: database/management/freeLOB description: If this flag is set to false, it controls the free memory calls defaultValue: true DATABASE_MANAGEMENT_FREEPAGEDBMAPPERLOB: settingName: database/management/freePageDBMapperLOB description: If this flag is set to false, it controls the free memory calls. defaultValue: true Following this change, restart the server.

INC-219341 · Issue 715051

Check added to ensure StepPage generation for Top keyword

Resolved in Pega Version 8.8

A ClassCastException was thrown when top page is used, indicating "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl cannot be cast to com.pega.pegarules.pub.clipboard.ClipboardPage". This has been resolved by adding a check which will generate a myStepPage for Keyword "Top" as necessary.

INC-219453 · Issue 715999

Security update enhanced to support custom implementations of InvokeAxis2

Resolved in Pega Version 8.8

The QueueProcessor activity indirectly invokes a Connect-SOAP. After installing the Security A22 patch, custom implementations on InvokeAxis2 reported runtime failure. This has been resolved by replacing reflection library use with explicit type checking and casting to get the array length in step 14 of InvokeAxis2.

INC-219627 · Issue 715995

InvokeHTTPConnector security updated

Resolved in Pega Version 8.8

"Allow invocation from browser" has been disabled for InvokeHTTPConnector, and "Require authentication to run" has been enabled. In addition, an unsafe reflection used to load JCIFS libraries for NTLM operations has been removed, which removes support for custom JCIFS libraries in Connect HTTP.

INC-219995 · Issue 717157

Security update enhanced to support custom implementations of InvokeAxis2

Resolved in Pega Version 8.8

The QueueProcessor activity indirectly invokes a Connect-SOAP. After installing the Security A22 patch, custom implementations on InvokeAxis2 reported runtime failure. This has been resolved by replacing reflection library use with explicit type checking and casting to get the array length in step 14 of InvokeAxis2.

INC-220031 · Issue 717167

Security update enhanced to support custom implementations of InvokeAxis2

Resolved in Pega Version 8.8

The QueueProcessor activity indirectly invokes a Connect-SOAP. After installing the Security A22 patch, custom implementations on InvokeAxis2 reported runtime failure. This has been resolved by replacing reflection library use with explicit type checking and casting to get the array length in step 14 of InvokeAxis2.

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