SR-B12850 · Issue 283836
SMA Garbage Collector landing page updated to work with updated browsers
Resolved in Pega Version 7.3
SMA's Garbage Collector landing page was not working correctly on the latest versions of Chrome and other browsers due to the document.all JavaScript function being deprecated. The code has been updated to correct this.
SR-B13020 · Issue 283559
Upgrade App Schema generates unique index name IDs
Resolved in Pega Version 7.3
Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.
SR-B13020 · Issue 283078
Upgrade App Schema generates unique index name IDs
Resolved in Pega Version 7.3
Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.
SR-B15143 · Issue 285148
Garbage Collector access fixed in Logging screen
Resolved in Pega Version 7.3
SMA Garbage Collector information was not available under Logging and Tracing due to a naming error; this has been fixed.
SR-B15499 · Issue 294497
SMA Remote Tracing works with URL encryption
Resolved in Pega Version 7.3
When URL encryption is enabled, Remote Tracing was not working from SMA. This occurred because the handling for the trace request coming from SMA was not triggering the URL encryption as needed, and has been fixed.
SR-B16328 · Issue 286668
BLOB data save performance improved
Resolved in Pega Version 7.3
In an installation with many large work objects, performance issues were seen when saving a BLOB. This was due to the BLOB still saving data for properties that had been removed, and has been resolved through better tracking of orphan entries of list type properties like string list and java object list.
SR-B26257 · Issue 288790
Fixed SMA broken item requeue
Resolved in Pega Version 7.3
When attempting to requeue a broken item using the SMA, the requeue failed with an error about Attribute Based Access Control. This was traced to the API passing a thread object that did not have any executable associated with it; the system will now create a new executable instance if the getThread().retrieveContext() is null.
SR-B2709 · Issue 276670
Fixed OOM exception during DL import on JVM
Resolved in Pega Version 7.3
An OOM exception was generated during DL import on JVM when the DL being deployed had an very large number of hotfixes relating to CarDirectories. This was traced to each directory deployment creating a new instance of JarLoaderTool to internally build the cache (VersionedJdbcJarReader) which was then never cleared from the Mbean cache. This has been corrected by adding a check to release memory.
SR-B31589 · Issue 301671
Workaround for Oracle SMA query timeout
Resolved in Pega Version 7.3
A bug in Oracle can cause an SMA query involving all-constraints to take a long time to execute, which in turn can cause RAP/application bundle imports to hang. The workaround for this is to set the Oracle parameter _optimizer_push_pred_cost_based to false before the execution of the SMA query involving all-constraints, then set it back to true after its execution at the session level.
SR-B31825 · Issue 288489
Documentation correction for service-enabled system management
Resolved in Pega Version 7.3
The help file for service-enabled system management has been updated to correct and clarify the full path used for connection properties in conjunction with the --connPropFile argument.