INC-183728 · Issue 665133
Oracle handling updated for primary key in upgrade DDL
Resolved in Pega Version 8.7
Previously, when a primary key of a table was created Oracle would automatically create a unique index with the same name as the primary key. However, with the introduction of Oracle 19, an optimization was added which will not do that if there is another unique index on the table which contains the column(s) of the primary key. This difference can cause updates to fail with the error "cannot drop index used for enforcement of unique/primary key". This has been resolved by updating the handling for primary key constraint and the corresponding index name.
SR-A18952 · Issue 236936
Request Only' I/O timeouts updated for Connect HTTP
Resolved in Pega Version 7.2.1
The Request Only checkbox option on Connect HTTP rules is intended to optimize IO latency for fire-and-forget use cases. The code that implements the connector was performing a full request/response HTTP call, even when the Request Only option had been selected. This sometimes caused long IO delays in the connectors. This update leverages the ability of the HTTP client to set a socket read timeout value on the response coming back from the server, which has now been set to 1 millisecond (zero milliseconds is not an option) in the cases when the Request Only feature has been enabled on the connector rule. The HTTP socket connection will time out immediately after the request message has been sent and eliminate any overhead of consuming the HTTP response data. Any connection failures will still be reported as exceptions.
SR-A19495 · Issue 237132
Request Only' I/O timeouts updated for Connect HTTP
Resolved in Pega Version 7.2.1
The Request Only checkbox option on Connect HTTP rules is intended to optimize IO latency for fire-and-forget use cases. The code that implements the connector was performing a full request/response HTTP call, even when the Request Only option had been selected. This sometimes caused long IO delays in the connectors. This update leverages the ability of the HTTP client to set a socket read timeout value on the response coming back from the server, which has now been set to 1 millisecond (zero milliseconds is not an option) in the cases when the Request Only feature has been enabled on the connector rule. The HTTP socket connection will time out immediately after the request message has been sent and eliminate any overhead of consuming the HTTP response data. Any connection failures will still be reported as exceptions.
SR-A21597 · Issue 241378
Request Only' I/O timeouts updated for Connect HTTP
Resolved in Pega Version 7.2.1
The Request Only checkbox option on Connect HTTP rules is intended to optimize IO latency for fire-and-forget use cases. The code that implements the connector was performing a full request/response HTTP call, even when the Request Only option had been selected. This sometimes caused long IO delays in the connectors. This update leverages the ability of the HTTP client to set a socket read timeout value on the response coming back from the server, which has now been set to 1 millisecond (zero milliseconds is not an option) in the cases when the Request Only feature has been enabled on the connector rule. The HTTP socket connection will time out immediately after the request message has been sent and eliminate any overhead of consuming the HTTP response data. Any connection failures will still be reported as exceptions.
INC-162262 · Issue 654966
Query added to find time zone for MSSQL database
Resolved in Pega Version 8.7
The exception "com.microsoft.sqlserver.jdbc.SQLServerException: xp_regread() returned error 5, 'Access is denied.'" was generated when the AES agent PushDBSizeInfo was being run. This was traced to the GetDBInfo activity trying to retrieve the time zone of the MSSQL database by executing a query that used a Microsoft SQL routine to read the windows registry to get the current time zone. The error was not due to security within the SQL Server, but instead was caused by Microsoft Windows security related to the permissions on the registry keys for the users under which specific SQL Server processes were running. To resolve this, an update has been made to call a different query which will get the time zone for the SQL Server.
INC-172849 · Issue 665983
SortPageList method updated for Obj-Sort
Resolved in Pega Version 8.7
Sorting page lists backed by a node level datapage using Obj-Sort was causing a ConcurrentModificationException. This has been resolved by updating the SorterImpl.sortPageList method to use java7CollectionsSort instead of collectionsSortWithInferenceEngineDisabled.
SR-A16058 · Issue 241525
Cookie handling updated for Silverlight Merged Word doc creation
Resolved in Pega Version 7.2.1
When trying to create a Merged Word Document using Silverlight based implementation, the Word session started but then generated the error "Failure to reattach server session" and the merge process did not occur. This was an issue where the HTTP requests sent from Silverlight WordMerge control did not contain all of the expected cookies if the cookies contained the equal (=) sign in them. The cookie parsing logic has been fixed to support cookies whose value contains equals (=) sign, and additional diagnostics have been added in the form of Cookies.xml. This file contains the list of cookies parsed from the cookie string retrieved from InternetGetCookieEx. SL adds these cookies to the HttpWebRequest object while making calls to Pega. This file gets created in the session folder (SLWord_*) in the temp directory.
SR-A21935 · Issue 247142
Corrected data page Lookup logic
Resolved in Pega Version 7.2.1
While trying to source a Datapage with Lookup, a "No records found" error was generated by the fetch using the pyClassName from parameter and considering that as primary page class instead of the data page page class. This has been corrected by using the pxObjClass from the parameter page, which is an actual data page class.
SR-A11695 · Issue 229147
EXCEPTION_BLACKOUT time calculation fixed
Resolved in Pega Version 7.2.1
When calculating the time for the EXCEPTION_BLACKOUT period in EmailListener, the dimensions were incorrect due to errors in the sleep time observed when email listener failed to establish connection. This has been fixed.
INC-171753 · Issue 649441
Checks for Apache Tomcat 6 with MSSQL removed
Resolved in Pega Version 8.7
After implementing a specific local Tomcat configuration that removed the Tomcat version number from displaying on Tomcat standard error screens, the error "Tomcat 6 not supported or unable to detect version for custom Tomcat: Apache Tomcat. Contact Pega Customer Support!" appeared and Tomcat failed to start. Because Tomcat 6 was not supported for use with Microsoft SQL Server Systems, Pega used the ServletContext.getServerInfo() method to determine the Tomcat version; if the system used Tomcat 6 or an undetermined version in combination with MSSQL then the system would purposefully not start. As Tomcat 6 is no longer supported in Pega 8.5.2 and above, this check is unnecessary in those versions and the Tomcat version 6 checks in ClassMapImpl have been removed to allow serverAllowsMerge to return as true.