INC-130304 · Issue 567925
Retry logic added for downloading upgraded rules
Resolved in Pega Version 8.2.8
A Rules upgrade failed while downloading applications from the maintenance server due to an SFTP server connection failure. This has been resolved by adding logic to retry if the first connection attempt fails.
INC-132218 · Issue 573358
Resolved buffer overflow for Migration loadDatabase
Resolved in Pega Version 8.2.8
A Rules upgrade failed in the Migration step at loadDatabase stage, involving the move of all the table records from old schema to new schema. This was traced to the inability of Migration to load blob of sizes more than 100 MB, and has been resolved by updating Migration to use byte[] to read the blob content with the help of metadata that contains blob length.
INC-133202 · Issue 574700
TableRenameUtil hashing improved
Resolved in Pega Version 8.2.8
During index name generation, the algorithm that was responsible for index name uniqueness was sometimes insufficient and cerated a loop condition. This has been resolved by using a stronger hash algorithm and refactoring the code that could result in a loop.
INC-148154 · Issue 602921
Hot Fix Manager updated to use installation order for schema import
Resolved in Pega Version 8.3.5
Schema changes were not being imported during the hot fix manager DL import process. Investigation showed this was due to hotfixes in the DL being iterated over from newest to oldest, causing older hotfixes to replace the value added to a map by the newer. To resolve this, the system has been updated to use hotfix install order, which considers selected and dependent hotfixes, rather than ordering newest to oldest. This ensures that newer table representations will override older rather than the other way around.
INC-130304 · Issue 567923
Retry logic added for downloading upgraded rules
Resolved in Pega Version 8.5.1
A Rules upgrade failed while downloading applications from the maintenance server due to an SFTP server connection failure. This has been resolved by adding logic to retry if the first connection attempt fails.
SR-A11447 · Issue 243018
Importing an archive no longer fails when using DynaTrace
Resolved in Pega Version 7.2.1
Importing an archive was failing when using the third party program DynaTrace. This was due to passivation during the import process, and the system has been modified to prevent this.
SR-A14359 · Issue 232227
Context-aware paths for SMA jmxclient.css and global.js files
Resolved in Pega Version 7.2.1
In some cases the jmxclient.css and global.js files were not found when running SMA due to the use of relative path names. The path names have now been made context-aware.
SR-A15710 · Issue 236472
Additional logging added to diagnose stale thread errors
Resolved in Pega Version 7.2.1
In order to better diagnose issues with stale threads, loggers have been added to the ThreadData class to capture and print any stack trace which is causing the thread to be cleared or destroyed. These loggers will only be printed whenever a stale thread error is thrown in order to maximize log space.
SR-A15710 · Issue 236472
Improved BIX extract handling for multiple active agents
Resolved in Pega Version 7.2.1
When multiple agents were scheduled to run extracts at the same time by utilizing pxExtractDataWithArgs, there was intermittent failure in creating the manifest files. The BIX log would not contain an entry for the files being created, no error was displayed, and agents sometimes needed to be restarted. This was an issue with incomplete extraction of the output data and manifest files due to the PAL timer overriding the current thread context as it handled each of the multiple calls. To resolve this, the previous static variables used to store thread and requester instances have been made private to ensure reliability when handling parallel extracts and simultaneous runs.
SR-A16337 · Issue 232778
OCXinstaller install.bat script for Windows explicitly sets .cab file path
Resolved in Pega Version 7.2.1
The OCXinstaller install.bat script for Windows failed if it was run from the command line in a directory other than the one the script was stored in. The root cause was the batch file not finding the actual .cab files, as the batch file assumes the cab files are in the current path. The install.bat file has been updated to always uses the path of the batch file as the current path.