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.

SR-A92260 · Issue 259866

GRS supported for JMS Listener ID

Resolved in Pega Version 7.2.2

Support has been added to use a global resource reference setting for the JMS listener Requestor ID field.

SR-A76100 · Issue 254315

GRS supported for JNDI settings in JMS Listener

Resolved in Pega Version 7.2.2

Support has been added to use global resource reference settings for the JNDI server field and the initial context factory field value in the JMS listener during test connections.

SR-A88782 · Issue 263961

GRS supported for JNDI settings in JMS Listener

Resolved in Pega Version 7.2.2

Support has been added to use global resource reference settings for the JNDI server field and the initial context factory field value in the JMS listener during test connections.

SR-A93038 · Issue 264675

Service REST requestor memory leak resolved

Resolved in Pega Version 7.2.2

The Asynchronous mode of executing Service REST acquired requestors from the pool while executing the queued jobs but did not return the requestors to the pool properly, causing a memory leak due to the requestors persisting in the system and not closing down. This has been fixed.

SR-A79631 · Issue 258414

XML generation switched to literal mode to handle encoding

Resolved in Pega Version 7.2.2

The encoded format of + was appearing in the outgoing XML stream due to the stream being generated with normal mode instead of literal. This has been changed.

SR-A79631 · Issue 257900

XML generation switched to literal mode to handle encoding

Resolved in Pega Version 7.2.2

The encoded format of + was appearing in the outgoing XML stream due to the stream being generated with normal mode instead of literal. This has been changed.

SR-A77003 · Issue 252758

GetFileAttachmentContent validates with Data-WorkAttachment- instead of File

Resolved in Pega Version 7.2.2

The SetEmailAttachments activity step 3 (java step) called a RUF pxGetFileAttachmentContent that always validated the pxObjClass with Data-WorkAttach-File. In order to support other classes of attachment, the validation process has been changed to Data-WorkAttachment- instead of File.

SR-A87728 · Issue 257771

Improved null namespace handling for WSDL import

Resolved in Pega Version 7.2.2

The SOAP Connector (Wizard) functionality in the Pega product was implemented and tested with the assumption that the WSDL document provided for consumption would contain a target namespace. Though not technically required, the great majority of WSDL documents meet this description. However, when using an imported WSDL that has no namespaces, the pxParseWSDL activity was passing a reported null namespace to some Axis2 activities that were not capable of safely consuming Definitions with null namespaces. This resulted in a "StringIndexOutOfBounds" error. To create more stability with the additional activities, WSDLParser has been updated to use QName objects themselves whenever possible and set the target namespace for the Definition to "" when it detects that it is null.

SR-A90147 · Issue 258936

Apache Commons FileUpload updated for increased security

Resolved in Pega Version 7.2.2

The version of Apache Commons FileUpload included with Tomcat has been updated to remove the potential of remote attackers causing a denial of service attack through CPU consumption via a long boundary string.

SR-A91799 · Issue 259729

Apache Commons FileUpload updated for increased security

Resolved in Pega Version 7.2.2

The version of Apache Commons FileUpload included with Tomcat has been updated to remove the potential of remote attackers causing a denial of service attack through CPU consumption via a long boundary string.

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