7.2.5 Notes about log files
-
Message logs are not output until the settings of all properties related to log output (beginning with logger) have been read successfully from the system definition file (jp1itslm.properties or jp1itslmur.properties).
If settings related to log output cannot be read successfully, ITSLM does not output log information to log files. When ITSLM is unable to output information to event logs, it terminates.
-
If an invalid value, such as an out-of-range value, is specified in a system definition file property related to log output (beginning with logger), ITSLM - Manager or ITSLM - UR assumes the default value and continues operation.
-
If you change the value of a system definition file property related to log output (beginning with logger) after the applicable properties have been read from the system definition file successfully, the change does not take effect until the process has been restarted.
-
If you change the value of any of the following system definition file properties, then before ITSLM is started you must move the folders and files that were output before the change was made to provide an empty system folder inside the message log output folder:
-
loggerCommandMessageFileCount
-
loggerCommandMessageMaxFileSize
-
loggerProcessCtrlMessageFileCount
-
loggerProcessCtrlMessageMaxFileSize
-
loggerWebSystemAnalysisMessageFileCount
-
loggerWebSystemAnalysisMessageMaxFileSize
-
-
For output of log files, ITSLM uses the default character encoding of the host on which ITSLM is running. Characters that are not supported by the default character encoding of the host on which ITSLM is running will result in garbled strings in the log files (garbled information in the log files).