INC-161984 · Issue 638856
Web Tier busy threads released on timeout
Resolved in Pega Version 8.6.1
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.
SR-D66986 · Issue 539411
BIX command line support improved
Resolved in Pega Version 8.3.2
Post-upgrade, it was seen that changes to the engine which validate that Data-Admin-DB-Name is not defined multiple times caused the BIX command line extracts to no longer work the same way. In order to improve backwards compatibility, updates have been made to loosen the validation in JdbcConfigurationFactory to always prefer prconfig settings if there are multiple definitions.
INC-178923 · Issue 660887
Resolved startup error related to business calendar object
Resolved in Pega Version 8.5.5
An error recorded in the log file when the server started was traced to a cache update that removed the old business calendar object and added the new business calendar object to the business cal list. This has been resolved by updating the system to replace the business calendar object instead of removing the old one from the cache first.
INC-151293 · Issue 630347
Out of memory condition resolved for BIX extraction
Resolved in Pega Version 8.6.1
A node was going down automatically during execution of a BIX Extract rule when working with old objects. Investigation showed this was related to an out of memory error: the work object had nested page lists, and when one of the page lists contained a propertylist which contained more records, the system was trying to add entries to the LinkedList if any properties were missing the reference during extraction. Because LinkedList allowed duplicates, it filled with enough errors to cause the out of memory condition. To resolve this, LinkedList has been replaced with LinkedHasSet, which does not allow duplicates.
SR-D63234 · Issue 529098
Blobless class handling updated in BIX extract
Resolved in Pega Version 8.3.2
When performing a BIX extract to database, null values were seen for some columns when there were values present in the clipboard and the report definition. Analysis showed that an Extract Rule defined on a Blobless class with a property having a length greater than 30 would return a null value even when the source table's corresponding columns do not have null values. This was due to BIX using an internal Report Definition which would truncate the column alias if the length of the column was greater than 30: when the extract then tried to find the actual property name in the result page, it did not find it and returned a null value. To resolve this, if the class is Blobless, the system will iterate over the property and check whether it is truncated or not. If it it truncated, the truncated name will be used when looking for the property in the result page instead of using the unmatching actual property name. This will ensure the correct value populated in the result page will be used.
INC-167611 · Issue 652467
Business users can move dashboard widgets on production portal pages
Resolved in Pega Version 8.6.1
Business users were not able to use "Edit dashboard" to move dashboard widgets in production portal pages. This was a missed use case of using an operator with different security level, and has been resolved by using the control pzUserDashboardIncludeScript instead of including pzpega_dashboard script directly in the UserPortal harness.
INC-211977 · Issue 713461
Handling added for large BIX Postgres data sets
Resolved in Pega Version 8.6.5
BIX extracts were causing timeouts or JVM out of memory errors. This was traced to the Postgres JDBC driver ignoring fetch size in auto-commit transaction mode, which led to everything being loaded into memory at once. To resolve this, changes have been added to support fetch size for large results when using PostgreSQL database for BIX Extraction.
SR-D63993 · Issue 524302
Resolved auto-addition of UpdateDateTime filter to BIX history extract
Resolved in Pega Version 8.3.2
When creating a BIX extract rule on history classes, trying to save the rule resulted in the invalid filter error "pxBIXReportPage—Cannot use a unexposed property". Analysis showed the pxUpdateDateTime column, which is the default filter on creating a new extract, was added automatically even though history classes do not have a pxUpdateDatetime column. While there was a workaround of manually removing the pxUpdateDateTime column filter when creating the extract rule for the first time, this has been resolved.
INC-217974 · Issue 715429
Handling added BIX extraction failure when called from custom activity
Resolved in Pega Version 8.6.5
After update, BIX extraction was failing but email from the schedulers indicated success. Investigation showed that when extract was called from a custom activity by calling pxExtractDataWithArgs, the stepStatusFail 'when' rule in the custom activity was not capturing all the exceptions specific to database extracts. This has been resolved by adding the necessary handling.
INC-169764 · Issue 645807
Decision table query performance improvements
Resolved in Pega Version 8.6.1
Severe latency was seen after update, and it was not possible to save business rule changes. This was traced to an issue with the decision rule being treated as a custom rule, and has been resolved by inserting a check. In addition, optimization has been added for queries on the pr_sys_decchg table.