APAR status
Closed as fixed if next.
Error description
The server's output log, which can be viewed from the settings page, is loaded twice before being displayed. Additionally, each time the page is changed, using pagination at the bottom of the viewer, the full log file will be loaded again. This occurs because the UI is trying to ensure that it has the latest lines from the log. However, this can cause performance problems when the log file is very large.
Local fix
limit the size of the log file size by changing your log4j.properties or download the log file and view it offline.
Problem summary
**************************************************************** * USERS AFFECTED: * * Log loaded multiple times * **************************************************************** * PROBLEM DESCRIPTION: * * Log loaded multiple times * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
PI94746
Reported component name
UC DEPLOY
Reported component ID
5725M5400
Reported release
627
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-03-06
Closed date
2018-06-19
Last modified date
2018-06-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"627","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
19 June 2018