Administration Console Online Help

Servers: Logging: General

In addition, you can use this page to specify the types of messages
that the server sends to standard out.

The server message log does not contain HTTP requests, JMS messages, or
JTA transaction messages. Instead, you can configure separate log files
for those requests and messages.

In addition to maintaining its local message log, by default, each
server forwards all messages of severity NOTICE and higher to
the domain log.

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. Usually
it is a computed value based on the name of the parent of this
MBean. For example, for a server log, it is
serverName.log.

However, if the name of the parent cannot be obtained, the file
name is weblogic.log. If you specify a relative
pathname, it is interpreted as relative to the server's root
directory.

To include a time and date stamp in the file name when the log
file is rotated, add java.text.SimpleDateFormat
variables to the file name. Surround each variable with percentage
(%) characters.

For example, if the file name is defined to be
myserver_%yyyy%_%MM%_%dd%_%hh%_%mm%.log, the log file
will be named myserver_yyyy_mm_dd_hh_mm.log.

When the log file is rotated, the rotated file name contains the
date stamp. For example, if the log file is rotated on 2 April,
2003 at 10:05 AM, the log file that contains the old 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. For example,
myserver.log00007.

Messages accumulate in a single file. You must erase the
contents of the file when the size is too large. Note that WebLogic
Server sets a threshold size limit of 500 MB before it forces a
hard rotation to prevent excessive log file growth.

SIZE

When the log file reaches the size that you specify in
FileMinSize, the server renames the file as
FileName.n.

TIME

At each time interval that you specify in TimeSpan,
the server renames the file as FileName.n.

After the server renames a file, subsequent messages accumulate
in a new file with the name that you specified in
FileName.

The size (1 - 65535 kilobytes) that triggers the server to move
log messages to a separate file. After the log file reaches the
specified minimum size, the next time the server checks the file
size, it will rename the current log file as
FileName.n and create a new one to store
subsequent messages. (Requires that you specify a file rotation
type of Size.)

The maximum number of log files that the server creates when it
rotates the log. This number does not include the file that the
server uses to store current messages. (Requires that you enable
Number of Files Limited.)

When enabled, this redirects the stdout of the JVM in which a
WebLogic Server instance runs, to the WebLogic logging system. The
stdout content is published to all the registered log destinations,
like the server terminal console and log file.

The size of the buffer for log messages that are sent to the
domain log. The buffer is maintained on the Managed Server and is
broadcasted to the domain log when it is full.

If you notice performance issues due to a high rate of log
messages being generated, set this value higher. This will cause
the buffer to be broadcasted less frequently from the Managed
Server to the domain log. In production environments, it is not
recommended to set the buffer size lower than the production
default of 10.