IBM Security Access Manager runtime messages
are messages that are produced by applications, commands, and utilities
that use the Security Access Manager 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.
Table 1. Message severity levels
and associated message logs| 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
Note: Logging
is not enabled by default.
|
| NOTICE_VERBOSE |
- C runtime log name
- msg__verbose.log
Note: Logging is not enabled
by default.
- Java runtime log name
- msg__app_nameN.log
- WebSEAL log name
- msg__verbose_PID.log
Note: Logging
is not enabled by default.
|
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 that are 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. You can change the name, location, and put size constraints
on the runtime message log files, as explained in Routing 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.