Names of runtime logs
ISAM runtime messages are messages that are produced by applications, commands, and utilities using the ISAM Runtime component. The sources include the C language-based utilities, such as the pdadmin commands and the svrsslcfg utility.
Table 1 lists the names of the default message log files for both C and Java™ language applications.
Notes:
Message severity Default log name FATAL
- C runtime log name
- msg__fatal.log
- Java runtime log name
- msg__app_nameN.log
- WebSEAL log name
- Written to the standard error file (STDERR)
ERROR
- C runtime log name
- msg__error.log
- Java runtime log name
- msg__app_nameN.log
- WebSEAL log name
- Written to the standard error file (STDERR)
WARNING
- C runtime log name
- msg__warning.log
- Java runtime log name
- msg__app_nameN.log
- WebSEAL log name
- Written to the standard error file (STDERR)
NOTICE
- C runtime log name
- msg__notice.log
- Java runtime log name
- msg__app_nameN.log
- WebSEAL log name
- msg__notice_PID.log Logging is not enabled by default.
NOTICE_VERBOSE
- C runtime log name
- msg__verbose.log Logging is not enabled by default.
- Java runtime log name
- msg__app_nameN.log
- WebSEAL log name
- msg__verbose_PID.log Logging is not enabled by default.
- When WebSEAL is running as a background process, FATAL, ERROR, and WARNING messages are redirected to the server message log file for that WebSEAL instance (msg__webseald-instance_name.log).
- If an application-specific configuration file does not exist for a Java application, message logs are controlled by the $JAVA_HOME/PolicyDirector/PDJLog.properties file. In these cases, messages are written to the following files:
By default, logging of NOTICE and NOTICE_VERBOSE messages is not enabled.
- FATAL
- msg__amj_fatalN.log
- ERROR
- msg__amj_errorN.log
- WARNING
- msg__amj_warningN.log
- NOTICE
- msg__amj_noticeN.log
- NOTICE_VERBOSE
- msg__amj_verboseN.log
Based on the severity level, runtime messages from C-language applications are written to different log files. For example, WARNING messages are written to the msg__warning.log file and FATAL messages are written to msg__fatal.log file. Error messages from WebSEAL are written to STDERR, unless WebSEAL is running in the background. In this case, the messages are written to the WebSEAL server log file.
Runtime message log files associated with C-language applications are allowed to grow without bound. Periodically check the available disk space and adjust as necessary, perhaps by archiving or pruning the log files. We can change the name, location, and put size constraints on the runtime message log files, as explained in Tracing configuration file entries. Runtime message log files for Java language applications can grow to a maximum size of 512 KB. A maximum of three message files can exist, with the most recent messages always being in the file that ends in
1. When the file reaches its maximum size, the files are renamed. For example, when the msg__appname1.log file reaches 512 KB, the following process occurs:
- The msg__appname3.log file is deleted, if it exists
- The msg__appname2.log file, if it exists, is renamed to msg__appname3.log
- The msg__appname1.log file is renamed msg__appname2.log
- A new msg__appname1.log file is created
The names, location, number, and size of the Java runtime logs can be changed, as explained in Table 1.
Parent topic: Names of message logs