INC-150610 · Issue 627428
Argument number exception handled for SERVICES-PAL log configuration
Resolved in Pega Version 8.5.3
An issue with being unable to configure the SERVICES-PAL log file has been resolved by adding handling for an unlogged "wrong number of arguments" exception.
INC-149382 · Issue 612427
Loading timing updated for openAPI content
Resolved in Pega Version 8.5.3
Open API content loading was taking too much time and interfering with working on other REST rule configurations. To resolve this, the loading of openAPI contents has been removed from the opening or saving of REST rule and shifted to lazy loading. Clicking on the openAPI tab will load the contents, and any modification in REST rule or service package rule will update the contents of openAPI when "Action->Refresh" is clicked.
INC-150809 · Issue 611856
Loading timing updated for openAPI content
Resolved in Pega Version 8.5.3
Open API content loading was taking too much time and interfering with working on other REST rule configurations. To resolve this, the loading of openAPI contents has been removed from the opening or saving of REST rule and shifted to lazy loading. Clicking on the openAPI tab will load the contents, and any modification in REST rule or service package rule will update the contents of openAPI when "Action->Refresh" is clicked.
INC-153664 · Issue 613054
Some general metrics now disabled by default for better performance
Resolved in Pega Version 8.5.3
While testing decisioning on fnx cloud platform, using a client application to simulate load and using the Stream service with Kafka Instaclustr as a backend, large latency spikes over 1,000 ms were observed at around 33 second intervals from Stream writes. Investigation identified that some metrics that are gathered every 30 sec (on every single node) include a "lag" calculation that requires a heavy process operation during which more threads are spun off, causing CPU spikes. To mitigate this, the general metrics are now disabled by default and can be enabled using DSS.
SR-D28719 · Issue 505967
Null archive check added to set import process status
Resolved in Pega Version 8.2.4
After running a 'prpcServiceUtils.sh import' which failed due to a low-level null pointer error, the job "IMPORTREQUEST-2" then incorrectly showed the status as 'IN PROGRESS' instead of 'FAILED'. In this case, the null pointer exception occurred because two imports were unintentionally happening at the same time: the process copied up the same set of archives to the service export directory, but the first import processed an archive and deleted it so that the second process failed to find it. When it exited with the null pointer exception, the status was not set to 'failed'. To resolve this, a null archive check has been added which will set the status to 'failed' if the archive is unsupported, corrupt, or not there at all.