Configuring and Managing WebLogic Server

Monitoring a WebLogic Server Domain

These sections describe WebLogic Server monitoring capabilities that help you manage and optimize application availability, performance, and security:

• Facilities for Monitoring WebLogic Server
• Monitoring WebLogic Server Using the Administration Console

 

---

Facilities for Monitoring WebLogic Server

These sections describe WebLogic Server facilities for monitoring the health and performance of a WebLogic Server domain:

• Administration Console
• Server Self-Health Monitoring
• Messages and Log Files

Administration Console

The WebLogic Server Administration Console provides visibility into a broad array of configuration and status information.

The Administration Console obtains information about domain resources from the domain's Administration Server. The Administration Server is populated with Management Beans (MBeans), based on Sun's Java Management Extension (JMX) standard, which provides the scheme for management access to domain resources.

The Administration Server contains:

• Configuration MBeans, which control the domain's configuration
• Run-time MBeans, which provide a snapshot of information about domain resources, such as JVM memory usage. When a resource in the domain—for instance, a Web application—is instantiated, a run-time MBean instance is created which collects information about that resource.

When you access a monitoring page for particular resource in the Administration Console, the Administration Server performs a GET operation to retrieve the current attribute values.

For details on what data is available on specific console pages, see Monitoring WebLogic Server Using the Administration Console.

Server Self-Health Monitoring

WebLogic Server provides a self-health monitoring feature to improve the reliability and availability of server instances in a domain. Selected subsystems within each server instance monitor their health status based on criteria specific to the subsystem. If an individual subsystem determines that it can no longer operate in a consistent and reliable manner, it registers its health state as "failed" with the host server instance.

Each server instance checks the health state of all its registered subsystems to determine the overall viability of the server. If one or more critical subsystems have reached the "failed" state, the server instance marks its own health state as "failed" to indicate that it cannot reliably host an application.

When used in combination with Node Manager, server self-health monitoring enables you to automatically reboot servers that have failed. This improves the overall reliability of a domain, and requires no direct intervention from an administrator. See Node Manager Capabilities for more information.

Obtaining Server Health Programmatically

You can check the self-reported health state of a server instance programmatically by calling the getHealthState() method on the ServerRuntimeMBean. Similarly, you can obtain the health state of a registered WebLogic Server subsystem by calling the getHealthState() method on its MBean. The following MBeans automatically register their health states with the host server:

• JMSRuntimeMBean
• JMSServerRuntimeMBean
• JTARuntimeMBean
• TransactionResourceRuntimeMBean

See the Javadocs for WebLogic Classes for more information on individual MBeans.

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.

 

---

Monitoring WebLogic Server Using the Administration Console

The left pane of the Administration Console is a tree control, with a node for key entities you have configured. The following sections list the attributes displays on monitoring pages in each node:

• Domain Monitoring Pages
• Server Monitoring Pages
• Clusters Monitoring Pages
• Machine Monitoring Pages
• Deployments Monitoring Pages
• Services Monitoring Pages

Domain Monitoring Pages

You can access one WebLogic domain at a time using the Administration Console. The Domain—>Monitoring tab provides access to key configuration attributes and the current state for the servers and clusters in the current domain. The following table lists the monitoring pages available for a domain, and the attributes displayed on each page.

Table 9-1 Domain Monitoring Pages

Console Page	Attributes Displayed
Domain->Monitoring->Server	Name Machine Listen Address Listen Port State SSL Listen Port
Domain->Monitoring->Cluster	Name Cluster Status Cluster Address Multicast Address Multicast Send Delay Configure Server Count Good Server Count Bad Server Count

Other Domain Monitoring Links

Each domain-level monitoring page has links to display:

• Domain Log—The Domain Log contains messages forwarded by all server instances in the domain.

Server Monitoring Pages

When expanded, the Servers node lists each server instance in the current domain. To monitor key run-time attributes for a server instance, click on its name, and choose one of Monitoring tabs. The monitoring pages available depend on the application objects deployed to the server instance. The following table lists the monitoring pages available for a server instance, and the attributes displayed on each page.

Table 9-2 Server Monitoring Pages

Console Page	Attributes Displayed
Server->Monitoring->General	State Activation Time WebLogic Version JDK Vendor JDK Version Operating System OS Version
Server->Monitoring->General Monitor All Active Queues...	Name Threads Idle Threads Oldest Pending Request Queue Length Throughput
Server->Monitoring->General Monitor all Connections...	Remote Address Remote JVMID Protocol Connect Time Bytes Sent Messages Received Messages Sent
Server->Monitoring->General Monitor all Active Sockets...	Remote Address Protocol
Server->Monitoring->Performance	Idle Threads Oldest Pending Request Throughput Queue Length Memory Usage
Server->Monitoring-> Security	Invalid Login Attempts Total Count User Lockout Total Count Login Attempts while Locked Total Count Invalid Login Users High Count Locked Users Current Count Unlocked Users Total Count
Server->JRockit	Used Heap Used Physical Memory Total Nursery Size Max Heap Size Gc Algorithm Total Garbage Collection Count Last GcEnd Last GcStart Total GcTime GCHandles Compaction Concurrent Generational Incremental Parallel Number Of Processors All Processors Average Load JVM Processor Load Total Number Of Threads Number Of Daemon Threads Uptime
Server->Monitoring->JMS	Current Connections Connections High Total Connections Current JMS Servers Servers High Servers Total
Server->Monitoring->JMS Monitor all Active JMS Connections...	Client ID Active sessions Most sessions Total sessions
Server->Monitoring->JMS Monitor all Active JMS Servers...	Server Connections Active JMS Destinations Session Pools Destinations Messages Bytes Current Bytes Pending Bytes Received Bytes Threshold Time Destinations High Destinations Total Messages High Messages Pending Messages Received Messages Threshold Time Name Session Pools High Session Pools Total
Server->Monitoring->JMS Monitor all Pooled JMS Connections...	Sessions Available Sessions Reserved Sessions Waiting Current Pool Capacity Maximum Pool Capacity Open Connections Average Sessions Reserved Creation Delay Time Highest Sessions Available Highest Sessions Not Available Highest Sessions Reserved Highest Sessions Waiting Highest Wait Seconds Leaked Sessions Name Refresh Failures Sessions Not Available Total Sessions Allocated Total Sessions Destroyed
Server->Monitoring->JTA	Total Transactions Total Committed Total Rolled Back Timeout Rollbacks Resource Rollbacks Application Rollbacks System Rollbacks Total Heuristics Total Transactions Abandoned Average Transactions Count Average Commit Time
Server->Monitoring->JTA Monitor all Transactions by Name	Name Total Transactions Total Committed Total Rolled Back Timeout Rollbacks Resource Rollbacks Application Rollbacks System Rollbacks Total Heuristics Total Transactions Abandoned Average Transactions Count Average Commit Time
Server->Monitoring->JTA Monitor all Transactions by Resource	Name Transactions Commits Rollbacks Heuristics Heuristic Commits Heuristic Rollbacks Mixed Heuristics Heuristic Hazards
Server->Monitoring->JTA Monitor all In-Flight Transactions	Transaction Id Name Status Seconds Active Servers Resources

Other Server Monitoring Links

Each top level tab page for a server instance—Performance, Security, JMS, JTA— has links to display:

• Server Log—The Server Log contains all messages generated by its subsystems and applications.
• JNDI Tree—The JNDI tree shows the objects deployed to the current server instance.

Clusters Monitoring Pages

The following table lists the monitoring pages available for a cluster, and the attributes displayed on each page

Table 9-3 Cluster Monitoring Pages

Console Page	Attributes Displayed
Domain->Cluster->Monitoring	Number of Servers configured for this cluster Number of Servers currently participating in this cluster Name State Servers Resend Requests Fragments Received Lost Multicast Messages

Machine Monitoring Pages

The following table lists the monitoring pages available for a machine, and the attributes displayed on each page.

Table 9-4 Machine Monitoring Pages

Console Page	Attributes Displayed
Machine-->Monitoring Node Manager Status	State bea.home weblogic.nodemanager.javaHome weblogic.nodemanager.listenAddress weblogic.nodemanager.listenPort CLASSPATH
Machine-->Monitoring Node Manager Log	See "Node Manager Logs" on page 4.

Deployments Monitoring Pages

The following table lists the monitoring pages available in the Deployments Node, and the attributes displayed on each page.

• Connector Deployments
• EJB Deployments
• Web Services Deployments
• Web Application Deployments

Connector Deployments

The following table lists the monitoring pages available for deployed Connectors and the attributes displayed on each page.

Table 9-5 Connector Deployments

Console Page	Attributes Displayed
Connector Modules	Connections Active Connections High Count Free Connections High Count Average Active Usage Connections Created Total Count Connections Matched Total Count Connections Destroyed Total Count Connections Rejected Total Count Connection Idle Profile Count Connection Idle Profiles Connection Leak Profile Count Connection Leak Profiles Number Detected Idle Number Detected Leaks Recycled Total

EJB Deployments

The following table lists the monitoring pages available for deployed EJBs and the attributes displayed on each page.

Table 9-6 EJB Deployments

Console Page	Attributes Displayed
EJB Modules->Message Driven EJBs	Pool Miss Ratio Destroyed Bean Ratio JMS Connection Alive Transaction Rollback Ratio Transaction Timeout Ratio Access Total Count Beans In Use Current Count Destroyed Total Count EJB Name Miss Total Count Pool Timeout Total Count Pool Waiter Total Count Pooled Beans Current Count Server Transactions Committed Total Count Transactions Rolled Back Total Count Transactions Timed out Total Count Waiter Current Count
EJB Modules->Stateless EJBs	Pool Timeout Total Count Pool Waiter Total Count Pooled Beans Current Count Server Transactions Committed Total Count Transactions Rolled Back Total Count Transactions Timed out Total Count Waiter Current Count
EJB Modules->Entity EJBs	Cache Miss Ratio Lock Manager Waiter Ratio Lock Manager Timeout Ratio Pool Miss Ratio Destroyed Bean Ratio Pool Timeout Ratio JMS Connection Alive Transaction Rollback Ratio Transaction Timeout Ratio Access Total Count Activation Count Beans In Use Current Count Cache Access Count Cache Miss Count Cached Beans Current Count Destroyed Total Count EJB Name Lock Mgr Access Count Lock Mgr Entries Current Count Lock Mgr Timeout Total Count Lock Mgr Waiter Total Count Miss Total Count Passivation Count Pool Timeout Total Count Pool Waiter Total Count Pooled Beans Current Count Server Transactions Committed Total Count Transactions Rolled Back Total Count Transactions Timed out Total Count Waiter Current Count
EJB Modules->Stateful EJBs	Cache Miss Ratio Lock Manager Waiter Ratio Lock Manager Timeout Ratio Transaction Rollback Ratio Transaction Timeout Ratio Activation Count Beans In Use Current Count Cache Access Count Cache Miss Count Cached Beans Current Count Destroyed Total Count EJB Name Lock Mgr Access Count Lock Mgr Entries Current Count Lock Mgr Timeout Total Count Lock Mgr Waiter Total Count Passivation Count Server Transactions Committed Total Count Transactions Rolled Back Total Count Transactions Timed out Total Count

Web Services Deployments

The following table lists the monitoring pages available for deployed Web Services and the attributes displayed on each page.

Table 9-7 Web Services Deployments

Console Page	Attributes Displayed
Web Service	Server Context Root Servlets Sessions Sessions High Total Sessions Machine Source Info
Sessions
Servlets	Servlet Name Servlet Path Machine Pool Max Capacity Reload Total Count Server Invocation Total Count Execution Time Average Execution Time High Execution Time Low Execution Time Total

Web Application Deployments

The following table lists the monitoring pages available for deployed Web Applications and the attributes displayed on each page.

Table 9-8 Web Application Deployments

Console Page	Attributes Displayed
Web Applications	Server Context Root Servlets Sessions Sessions High Total Sessions Machine Source Info
Servlets	Servlet Name URLPatterns Server Invocation Total Count Execution Time Average Execution Time High Execution Time Low Execution Time Total Machine Name Pool Max Capacity Reload Total Count Servlet Path
Sessions

Services Monitoring Pages

The following table lists the monitoring pages available in the Services node, and the attributes displayed on each page.

Table 9-9 JDBC Monitoring Pages

Console Page	Attributes Displayed
JDBC->Connection Pools	Server State Connections Waiters Num Unavailable Active Connections Average Connections Delay Time Connections High Connections Total Curr Capacity Driver Version Failures to Reconnect Count Highest Num Unavailable Max Capacity Wait Seconds High Waiters High

Table 9-10 JMS Deployments

Console Page	Attributes Displayed
JMS Connection Factory	Name JNDIName Client Id Default Priority Default Time To Live Default Redelivery Delay
JMS Server Monitor Active JMS Servers	Name Server Connections Active JMS Destination Session Pools Destinations Messages Bytes Current Bytes Pending Bytes Received Bytes Threshold Time Destinations High Destinations Total Messages High Messages Pending Messages Received Messages Threshold Time Messages Maximum Session Pools High Session Pools Total
JMS Server Monitor Active JMS Destinations	Name Consumers Consumers High Consumers Total Messages Messages High Messages Pending Messages Received Messages Threshold Time Messages Maximum Bytes Bytes Pending Bytes Received Bytes Threshold Time
JMS Server Monitor JMS Session Pools	Name Store Temporary Template Bytes Maximum Messages Maximum
Monitor Durable Subscribers	Client ID Subscription Name No Local Active Selector Messages Pending Count Messages Current Count Bytes Pending Count — Bytes Current Count
Active JMS Producers	Bytes Pending Bytes Sent Messages Pending Messages Sent
Active JMS Consumers	Name Active Selected Durable Messages Pending Messages Received Bytes Pending Bytes Received