Technical data

6 Using Log Messages to Manage WebLogic Servers
6-6 Administration Guide
Client Logging
Java clients that use the WebLogic logging facility may also generate log messages.
However, messages logged by clients are not forwarded to the domain log. You
configure logging properties of a client by entering the appropriate argument on the
command line:
-Dweblogic.log.attribute=value
where attribute is any LogMBean attribute.
By default, logging to a log file is turned off for clients and messages are logged to
stdout. You can turn on logging to a file and set the file name for the log if you
include the following argument on the command line:
-Dweblogic.log.FileName=logfilename
where logfilename is the name that you want to use for the client log file.
The following command line arguments can also be used for client logging:
-Dweblogic.StdoutEnabled=boolean
-Dweblogic.StdoutDebugEnabled=boolean
-Dweblogic.StdoutSeverityLevel = [64 | 32 | 16 | 8 | 4 | 2 | 1 ]
where boolean is either true or false and the numeric values for
StdoutSeverityLevel correspond to the following severity levels:
INFO(64) WARNING(32), ERROR(16), NOTICE(8), CRITICAL(4), ALERT(2) and
EMERGENCY(1).
Log File Format
The first line of each message in a log file begins with #### followed by the message
header. The message header provides the run-time context of the message. Each
attribute of the message is contained between angle brackets.
Lines following the message body are only present for messages logging an exception
and display the stack trace for the exception. If a message is not logged within the
context of a transaction, the angle brackets (separators) for Transaction ID are present
even though no Transaction ID is present.