Technical data

Local Server Log Files
Administration Guide 6-5
For example, if you enter the following value in the File Name field:
myserver_%yyyy%_%MM%_%dd%_%hh%_%mm%.log
the server’s log file will be named:
myserver_yyyy_MM_dd_hh_mm.log
When the server instance rotates the log file, the rotated file name contains the date
stamp. For example, if the server instance rotates its local log file on 2 April, 2003 at
10:05 AM, the log file that contains the old log messages will be named:
myserver_2003_04_02_10_05.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. For example:
myserver.log00007.
By default, the local server log file is called
servername.log (where servername is
the name of the server) and is created in the directory where you started the WebLogic
Server. You can set the file name also on the Configuration
→Logging page for the
server.
You can specify the maximum number of rotated files that can accumulate by setting
an appropriate value for the
File Count field. Once the number of log files reaches
this number, the oldest log file is deleted each time a log file rotation occurs.
The local server log always has all the messages that have been logged.
Configuring logging by the local server also includes the ability to specify which
messages are logged to
stdout. You can exclude messages of lower severity by
specifying the lowest severity to be logged. You can also enable or disable logging of
debug messages to
stdout.
Note: It is recommended that you not modify the server log files by manually editing
them. Log rotation by time is based on the timestamp of the files. If you
modify the file, this changes the timestamp and log rotation may become
confused. If you edit the file manually this may lock the file and prevent
updating of the file by the server.