The Server—>Logging—>General tab configures the server message log for a WebLogic Server instance. Use it to specify the name of the log file and the types of messages that the server sends to standard out in addition to the log file.
Each server keeps its own message log. In addition, by default, a server forwards all messages of serverity ERROR and higher to the domain log. To change this default, create a domain log filter.
The server message log does not contain HTTP requests, JDBC messages, or JTA transaction messages. Instead, you can configure separate log files for those requests and messages.
Debug Messages
If you create applications to run on WebLogic Server, you can configure your applications to generate messages of severity DEBUG. These messages are never forwarded to the domain log and are intended to contain detailed information about the operation of an application or the server.
The name of the file that stores current log messages. If the pathname is not absolute, the path is assumed to be relative to the root directory of the machine on which the server is running.
If the name does not include a path element, then pathname will be computed as follows:
For a server log file, ./SERVER_NAME
For a domain log file, ./
If neither file name nor pathname is specified, then the name is computed as follows:
For a server log file, ./SERVER_NAME/SERVER_NAME.log
For a domain log file, ./DOMAIN_NAME.log
To include a time or date stamp in the file name when the log file is rotated, add java.text.SimpleDateFormat variables. Surround each variable with percentage (%) characters.
For example, myserver_%yyyy%_%MM%_%dd%_%hh%_%mm%.log
If you do not include a time and date stamp, the rotated log files are numbered in order of creation filenamennnnn, where filename is the name configured for the log file.
Enables the server to send messages to standard out in addition to the log file. Use StdoutDebugEnabled and StdoutSeverityLevelto determine the type of messages that the server sends to standard out.
Determines whether the server sends messages of the DEBUG severity to standard out in addition to the log file. You must enable Log to Standard Outfor this property to be relevant.
The minimum severity of a message that the server sends to standard out. You must enable Log to Standard Out for this value to be relevant.
The ascending order of severities is as follows:
INFO(64). Used for reporting normal operations.
WARNING(32). A suspicious operation or configuration has occurred but it may not have an impact on normal operation.
ERROR(16). A user error has occurred. The system or application is able to handle the error with no interruption, and limited degradation, of service.
NOTICE(8). An INFO or WARNING-level message that is particularly important for monitoring the server. Only WebLogic Server subsystems write messages of this severity type.
CRITICAL(4). A system or service error has occurred. The system is able to recover but there might be a momentary loss, or permanent degradation, of service.
ALERT(2). A particular service is in an unusable state while other parts of the system continue to function. Automatic recovery is not possible; the immediate attention of the administrator is needed to resolve the problem.
EMERGENCY(1). The server is in an unusable state. This severity indicates a severe system failure or panic.
