Weblogic Messages and Log Files

Messages and Log Files

WebLogic Server records information about events such as configuration changes, deployment of applications, and subsystem failures in log files. The information in log files is useful for detecting and troubleshooting problems, and monitoring performance and availability.

For detailed information about log files and the WebLogic Server logging subsystem, see Logging in Administration Console Online Help.

WebLogic Server outputs status and error messages to:

• Standard Out—By default, a WebLogic Server instance prints all messages of WARNING severity or higher to standard out—typically the command shell window in which you are running the server instance. You can control what messages a server instance writes to standard out using the Server—>Logging tab.

If you start a Managed Server with Node Manager, Node Manager redirects the server instance's standard out to a file. In this case, you can view the Managed Server's output using Domain—>Server—>Remote Start Output—>View Server output.

• Standard Error—A WebLogic Server instance writes errors to standard error—typically the command shell window in which you are running the server instance.

If you start a Managed Server with Node Manager, Node Manager redirects the server instance's standard error to a file. In this case, you can view the Managed Server's output using Domain—>Server—>Remote Start Output—>View Server error output.

• Node Manager Output—If you start a Managed Server with Node Manager, you can access Node Manager output using Domain—>Server—>Remote Start Output—>View Node Manager output.
• Server Logs—Each WebLogic Server instance writes all messages from its subsystems and applications to a log file on its host machine. You can configure logging behavior using the Server—>Logging—>Server tab. You can view a server instance's log file using the View server log link on any server tabs page.
• Domain Log—By default, each server instance in a domain forwards all messages from its subsystems and applications to the Administration Server for the domain. The Administration Server writes a subset of the messages to the Domain Log. You can control whether or not a server instance sends its messages to the Administration Server, and configure filters that control which messages it sends using the Server—>Logging—>Domain tab. You can view the Domain Log using the View domain log link on any domain tab page.

An incorrect timestamp might be displayed for the domain log when multiple managed servers create the log files simultaneously. A difference in timestamp might also be observed when multiple components create logs even though the same managed server creates them.

• Node Manager Logs—Node Manager writes startup and status messages to a log file in the WL_HOME\common\nodemanager\NodeManagerLogs\NodeManagerInternal directory. Node Manager log files are named NodeManagerInternal_timestamp, where timestamp indicates the time at which Node Manager started.
• HTTP Logs—By default, each server instance maintains a log of HTTP requests. Disable HTTP logging, or configure logging behavior using the Server—>Logging—>HTTP tab.
• JTA Logs—Configure a server instance to maintain a JTA transaction log using the Server—>Logging—>JTA tab.
• JDBC Logs—Configure a server instance to maintain a JDBC log using the Server—>Logging—>JDBC tab.