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-160198 · Issue 632905

Enhancement added for attachment size handling with Kafka

Resolved in Pega Version 8.6

Attempting to send an email attachment larger than 2 MB resulted in the error "Caused by: org.apache.kafka.common.errors.RecordTooLargeException: The message is 8101592 bytes when serialized which is larger than the maximum request size you have configured with the max.request.size configuration." This has been resolved by updating the Stream SPI size to 2.0.5-14 to support custom producer configurations. The settings can be passed as environment parameters, for example 'Dstream.producer.max.request.size=500990'.

INC-160288 · Issue 626067

Kerberos handling updated for database remap

Resolved in Pega Version 8.6

After upgrade from Pega v7.2 to Pega v8.4, using Kerberos authentication was failing during the remap task. Investigation showed that null username and password values were being passed to SchemaAssignmentUtility along with the flags as arguments, causing the utility to misinterpret the arguments. As arguments should be populated only when flags and values are available and not null, an update has been made which will set the username and password flags only if they are not null in the Remap database tables target.

INC-160382 · Issue 630714

Added handling for double quotes when converting tables

Resolved in Pega Version 8.6

After importing some packages from development to production, DDL conversion failed for tables with 30 characters in the table name when the import file contained a "Create VIEW" sentence. This was due to the addition of double quotes (" "). The table rename utility was not expecting to handle quoted table names, so as a result the addition of the quotation mark characters were included in the length calculation, and when renaming was performed it yielded syntactically invalid names (with leading " in the name). To resolve this, an update has been made which will strip quotes from table names being passed into TableRenameUtil.

INC-162360 · Issue 635817

Unneeded AUC error percentage calculation removed for better system performance

Resolved in Pega Version 8.6

When generating snapshots of the ADM models, an inefficiency in the metric calculation for the AUC error percentage caused an excessive amount of memory to be allocated which could cause slowdown or require a system reboot. This has been resolved by removing the problematic AUC error percentage calculation as it is not used in the UI.

INC-163940 · Issue 634491

CustomerData schema added to list of databases for optimization

Resolved in Pega Version 8.6

was no "Create?" column. This column appeared for the PegaDATA database but not for CustomerData. To resolve this, the Optimize Schema Landing Page has been updated to treat the CustomerData schema as a shipped Pega database.

INC-159834 · Issue 632248

StackOverFlow logging improved

Resolved in Pega Version 8.5.4

Enhanced diagnostic logging information has been added to help find issues when StackOverFlow errors occur.

INC-161984 · Issue 638857

Web Tier busy threads released on timeout

Resolved in Pega Version 8.5.4

Tomcat Web Tier Busy Threads were not being correctly released, causing stability and performance problems that included health check pings not receiving a thread to service the request so the node was marked as bad, users were quiesced, and the node replaced. Investigation showed the 'put' on the blocking queue did not time out when the queue was full and waited indefinitely, keeping the thread blocked. To resolve this, the system will use 'offer' on the blocking queue instead of 'put' to force thread release on timeout. In addition, debug logs have been added to understand when the offer (or Put) does not succeed and the state of the queue that is causing this issue; the debug logs for class com.pega.pegarules.session.internal.serverpush.RoboticAutomationImpl should be enabled only if the thread busy issue is observed and for limited time window while actively debugging.

INC-164794 · Issue 637992

Apache Commons libraries updated

Resolved in Pega Version 8.5.4

Apache commons-codec has been updated to version 1.15 , and Apache commons-io has been updated to version 2.7.

INC-171587 · Issue 652187

Resolved Push Node Daily Information exception

Resolved in Pega Version 8.5.4

The "Push Nodes Info Daily" agent was generating an exception on each of the nodes. This has been resolved by enhancing the PegaAESRemote code to handle the exception and get the node info locally, then push it to the console when it is not able to get it via the cluster management API.

INC-173162 · Issue 650794

Certificate match will use Subject Distinguished Name

Resolved in Pega Version 8.5.4

Signature verification was failing due to the system not finding the matching root certificate for the chain. The root certificate was in the trust store, but the system found a different certificate first and that other certificate (an intermediate certificate) was not considered a valid certificate for validating the whole certificate chain. This was traced to filtering on the Issuer Distinguished Name (DN) instead of the Subject DN and was due to intermediate certificates potentially having the same Issuer as a root certificate (e.g. if that root certificate was used to create the intermediate certificate). To resolve this, an update has been made to check the Subject DN instead of Issuer DN.

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