| |
Servers: Logging: General
Configuration Options Advanced Configuration Options Related Tasks Related Topics
Use this page to define the general logging settings for this server.
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
NOTICEand 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.Configuration Options
Name Description Log file name 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
SERVER_NAME.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.SimpleDateFormatvariables 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 namedmyserver_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 for the first time 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.log00001.If you do not include a time and date stamp, the rotated log files are numbered in order of creation. For example,
myserver.log00007.MBean Attribute:
LogMBean.FileNameChanges take effect after you redeploy the module or restart the server.
Rotation type Criteria for moving old log messages to a separate file.
NONEMessages 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.
SIZEWhen the log file reaches the size that you specify in
FileMinSize, the server renames the file asSERVER_NAME.lognnnnn.TIMEAt each time interval that you specify in
TimeSpan, the server renames the file asSERVER_NAME.lognnnnn.After the server renames a file, subsequent messages accumulate in a new file with the name that you specified as the log file name.
MBean Attribute:
LogMBean.RotationTypeSecure value:
byTimeChanges take effect after you redeploy the module or restart the server.
Rotation file size The size (1 - 65535 kilobytes) that triggers the server to move log messages to a separate file. The default is 500 kilobytes. 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
SERVER_NAME.lognnnnnand create a new one to store subsequent messages. (Requires that you specify a file rotation type ofSize.)MBean Attribute:
LogMBean.FileMinSizeMinimum value:
1Maximum value:
65535Begin rotation time Determines the start time (hour and minute) for a time-based rotation sequence.
At the time that this value specifies, the server renames the current log file. Thereafter, the server renames the log file at an interval that you specify in File Time Span.
Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth.
Use the following format:
H:mm, where
His Hour in day (0-23).
mmis the minute in hour
MBean Attribute:
LogMBean.RotationTimeRotation interval The interval (in hours) at which the server saves old log messages to another file. (Requires that you specify a file rotation type of
TIME.)MBean Attribute:
LogMBean.FileTimeSpanMinimum value:
1Limit number of retained files Indicates whether to limit the number of log files that this server instance creates to store old messages. (Requires that you specify a file rotation type of
SIZEorTIME.)After the server reaches this limit, it deletes the oldest log file and creates a new log file with the latest suffix.
If you do not enable this option, the server creates new files indefinitely and you must clean up these files as you require.
MBean Attribute:
LogMBean.NumberOfFilesLimitedFiles to retain 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.)
MBean Attribute:
LogMBean.FileCountMinimum value:
1Maximum value:
99999Log file rotation directory The directory where the rotated log files will be stored. By default the rotated files are stored in the same directory where the log file is stored.
MBean Attribute:
LogMBean.LogFileRotationDirChanges take effect after you redeploy the module or restart the server.
Rotate log file on startup Specifies whether a server rotates its log file during its startup cycle.
MBean Attribute:
LogMBean.RotateLogOnStartupChanges take effect after you redeploy the module or restart the server.
Advanced Configuration Options
Name Description Date Format Pattern The date format pattern used for rendering dates in the log. The DateFormatPattern string conforms to the specification of the
java.text.SimpleDateFormatclass.MBean Attribute:
LogFileMBean.DateFormatPatternChanges take effect after you redeploy the module or restart the server.
Logging implementation Specifies whether the server logging is based on a Log4j implementation. By default, WebLogic logging uses an implementation based on the Java Logging APIs which are part of the JDK.
Applications that use the WebLogic Message Catalog framework or the NonCatalogLogger will not be affected by the underlying Logging implementation.
MBean Attribute:
LogMBean.Log4jLoggingEnabledChanges take effect after you redeploy the module or restart the server.
Severity level The minimum severity of log messages going to the server log file. By default all messages go to the log file.
MBean Attribute:
LogMBean.LogFileSeverityFilter The filter configuration for the server log file.
A filter configuration defines simple filtering rules to limit the volume of log messages written to the log file.
MBean Attribute:
LogMBean.LogFileFilterLog File Buffer Gets the underlying log buffer size in kilobytes
MBean Attribute:
LogFileMBean.BufferSizeKBChanges take effect after you redeploy the module or restart the server.
Redirect stdout logging enabled 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.
MBean Attribute:
LogMBean.RedirectStdoutToServerLogEnabledChanges take effect after you redeploy the module or restart the server.
Redirect stderr logging enabled When enabled, this redirects the stderr of the JVM in which a WebLogic Server instance runs, to the WebLogic Logging system. The stderr content is published to all the registered log destinations, like the server terminal console and log file.
MBean Attribute:
LogMBean.RedirectStderrToServerLogEnabledChanges take effect after you redeploy the module or restart the server.
Logging Bridge Uses Parent Loggers Specifies whether application log messages are propagated to the parent node in the Logger tree or to the WebLogic Server log by means of the Logging Bridge. By default, this attribute is disabled, which results in application log messages being propagated to the WebLogic Server log.
Note the following behavior:
If WebLogic Server is configured to be based upon the Java Logging API (the default), the Logging Bridge is made available as a
java.util.logging.Handlerobject.If WebLogic Server is configured to be based upon a Log4j implementation, the Logging Bridge is made available as a
org.apache.log4j.Appenderobject.If the
ServerLoggingBridgeUseParentLoggersEnabledis disabled, applications that use either the Java Logging API or Log4j have their log messages redirected by the Logging Bridge to the WebLogic Server log.If the
ServerLoggingBridgeUseParentLoggersEnabledis enabled, applications that use the Java Logging API have their log messages propagated to the parent node in the global Java Logging Logger tree.If the
ServerLoggingBridgeUseParentLoggersEnabledis enabled, applications that use Log4j have their log messages propagated to the parent node in the Log4j Logger tree.MBean Attribute:
LogMBean.ServerLoggingBridgeUseParentLoggersEnabledChanges take effect after you redeploy the module or restart the server.
Severity level The minimum severity of log messages going to the standard out. Messages with a lower severity than the specified value will not be published to standard out.
MBean Attribute:
LogMBean.StdoutSeverityFilter The filter configuration for log events being sent to the standard out.
MBean Attribute:
LogMBean.StdoutFilterSeverity level The minimum severity of log messages going to the domain log from this server's log broadcaster. Messages with a lower severity than the specified value will not be published to the domain log.
MBean Attribute:
LogMBean.DomainLogBroadcastSeverityFilter The filter configuration for log events being sent to the domain log.
MBean Attribute:
LogMBean.DomainLogBroadcastFilterBuffer Size Broadcasts log messages to the domain log in batch mode.
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.
MBean Attribute:
LogMBean.DomainLogBroadcasterBufferSizeMinimum value:
1Maximum value:
100Memory Buffer Severity level The minimum severity of log messages going to the memory buffer of recent log events. Messages with a lower severity than the specified value will not be cached in the buffer.
MBean Attribute:
LogMBean.MemoryBufferSeverityMemory Buffer Filter The filter configuration for messages that are stored in the log memory buffer. By default, all log messages are cached.
MBean Attribute:
LogMBean.MemoryBufferFilterMemory Buffer Size The size of the memory buffer that holds the last n log records. This is used to support viewing the most recent log record entries (tail viewing) from the WebLogic Administration Console.
MBean Attribute:
LogMBean.MemoryBufferSizeMinimum value:
100Maximum value:
5000Stack Traces to stdout Specifies whether to dump stack traces to the console when included in logged message.
MBean Attribute:
CommonLogMBean.StdoutLogStackstdout Stack Trace Depth Determines the no of stacktrace frames to display on standard out. All frames are displayed in the log file. * -1 means all frames are displayed.
stdout Format The output format to use when logging to the console.
MBean Attribute:
CommonLogMBean.StdoutFormatChanges take effect after you redeploy the module or restart the server.
Minimum severity to log The minimum severity of log messages going to all log destinations. By default all messages are published.
MBean Attribute:
CommonLogMBean.LoggerSeverityLogger severity properties The configuration of the different logger severities keyed by name. The values are one of the predefined Severity strings namely Emergency, Alert, Critical, Error, Warning, Notice, Info, Debug, Trace.
MBean Attribute:
CommonLogMBean.LoggerSeverityProperties
|
