> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Oracle WebLogic Server Monitoring

> Catch stuck threads, exhausted JDBC pools and backed-up JMS queues on every WebLogic server before your applications slow down.

Components
[`Engine`](https://docs.germainux.com/deploy/germain-ux-engine)
[`JS Profiler`](https://docs.germainux.com/deploy/germain-ux-js-profiler)
[`RPA Bot Recorder`](https://docs.germainux.com/deploy/germain-ux-rpa-bot-recorder)
[`RUM JS`](https://docs.germainux.com/deploy/germain-ux-rum-js)
[`RUM Extension`](https://docs.germainux.com/deploy/germain-ux-rum-extension)

Availability
8.6.9 or later

> [card] [What Is Monitored](#what-is-monitored)
>
> Threads, JDBC, JMS, JTA

> [card] [How It Works](#how-it-works)
>
> JMX monitor per server

> [card] [Deploy](#deploy)
>
> One wizard run per server

> [card] [KPIs](#kpis)
>
> 31 WebLogic KPIs

## Overview

GermainUX reads the runtime state of each WebLogic Server over JMX and turns it into KPIs. You see the execute thread pool with its hogging and stuck threads, every JDBC data source and how many requests wait for a connection, the depth of each JMS destination, and transaction commits and rollbacks. Thirty-one KPIs, default SLAs on server state and health, and a **Weblogic Overview** dashboard come ready to use. Your team finds the server, data source or queue behind a slow application without opening the WebLogic console on each server.

> [card] Stuck and Hogging Threads
>
> Total, idle, standby, hogging and stuck execute threads on each server, so thread starvation shows before requests time out.

> [card] JDBC Pool Pressure
>
> Active, available and leaked connections, and requests waiting for a connection or failing to get one, per data source.

> [card] JMS Backlogs
>
> Current and pending messages and the number of consumers on each JMS destination.

> [card] Server State and Health
>
> Whether each server is `RUNNING` and reports `HEALTH_OK`, with a default SLA on both.

### Questions It Answers

* Which WebLogic server has stuck threads right now, and since when?
* Is a JDBC data source out of connections, and are requests failing to get one?
* Is a JMS queue backing up because its consumers stopped?
* Are more transactions rolling back than usual?
* Which servlets are slowest, and in which application?
* Is every server running and healthy?
* Did a data source stop running, for example during a database failover?

## What Is Monitored

| Area | What GermainUX monitors |
| - | - |
| **Threads** | Total, idle, standby, hogging and stuck threads of the execute thread pool on each server |
| **JDBC data sources** | State, current capacity, active connections (current, average and highest), available and unavailable connections, leaked connections, requests waiting for a connection, and wait failures |
| **JMS destinations** | Current, pending and received messages, and the number of consumers on each destination |
| **Transactions** | Total, committed and rolled-back JTA transactions since the server started |
| **Server** | Server state, such as `RUNNING`, and health state, such as `HEALTH_OK` |
| **Servlets** | Invocations and the lowest, highest, average and total execution time of each servlet, per application and web module |
| **Work managers** | Completed and pending requests of each work manager, per application |
| **Availability** | Up/down status and response time of the URLs your WebLogic applications serve, checked on a schedule with [synthetic HTTP checks](https://docs.germainux.com/automation/synthetic-http-execution.md) |
| **Logs** | Errors and warnings from the server logs, with [File and Log Monitoring](https://docs.germainux.com/integrations/file-log-monitoring.md) |
| **Host** | CPU, memory, disk and network of the WebLogic hosts, and whether the server process is running. See [Linux monitoring](https://docs.germainux.com/integrations/linux-redhat-suse-monitoring.md) or [Windows monitoring](https://docs.germainux.com/integrations/windows-monitoring.md). |
| **User experience** | Real-user page performance, JavaScript errors and Session Replay for the applications WebLogic hosts, with [RUM JS](https://docs.germainux.com/deploy/germain-ux-rum-js.md) or the [RUM Extension](https://docs.germainux.com/deploy/germain-ux-rum-extension.md) |

## Analytics, Alerts and Automation

### AI Analysis

Ask [AI Explore](https://docs.germainux.com/analytics/ai-driven-insights.md) questions such as "Which WebLogic data sources had requests waiting for a connection this week?" [Outlier detection](https://docs.germainux.com/analytics/outlier-detection.md) flags a thread count, queue depth or rollback count outside its normal range.

### Dashboards and Reports

In the left menu, go to **Dashboards > All**, and then open the **Weblogic Overview** dashboard. It has one chart or table for each of the 31 WebLogic KPIs: trend charts for threads, transactions and JDBC waits, and tables for data sources, JMS destinations, server state, servlets and work managers. Click a chart to open its KPI and break it down by server or by name. You can build your own [dashboards and reports](https://docs.germainux.com/dashboards/dashboard-and-report.md) on the same KPIs.

![Weblogic Overview dashboard over six hours, with JMS consumer and message tables, hogging and stuck thread charts peaking at 1:00 pm, idle, standby and total execute thread charts, and JTA committed, rolled back and total transaction charts](https://mintcdn.com/germain-ux/ES2SyPExMrRBE5X6/images/main/oracle-weblogic-monitoring/weblogic-overview-dashboard.png?fit=max\&auto=format\&n=ES2SyPExMrRBE5X6\&q=85\&s=29414c6af545b310cdb83c3e832054ee)

Weblogic Overview Dashboard - GermainUX

### Analysis

Click a value on the dashboard to open it in the [Analysis](https://docs.germainux.com/dashboards/analytics-dashboard/4-analysis-dashboard.md) screen. It compares the selected period with earlier ones, and the breakdown shows which server, data source or destination changed most.

![Analysis screen for the WebLogic Stuck Threads KPI, with a rise in stuck threads and the server wls-02 as the leading factor](https://mintcdn.com/germain-ux/ES2SyPExMrRBE5X6/images/main/oracle-weblogic-monitoring/weblogic-stuck-threads-analysis.png?fit=max\&auto=format\&n=ES2SyPExMrRBE5X6\&q=85\&s=f082a9b959162b7b5dbffe9775650380)

Analysis of WebLogic Stuck Threads - GermainUX

### Investigate an Exhausted JDBC Pool

When requests slow down or fail to reach the database, open the **WebLogic JDBC Waiting For Connection Current Count** KPI in the [Analysis](https://docs.germainux.com/dashboards/analytics-dashboard/4-analysis-dashboard.md) screen. The top row compares the average number of waiting requests with the previous days and shows the hourly trend. The relationships chart shows when the requests started to wait, and the segmentation breakdown lists what changed most. Then open **WebLogic JDBC Waiting For Connection Failure Total** and **WebLogic JTA Transaction Rolled Back Total Count** to see whether requests gave up and transactions rolled back.

In the example below, a batch job locks the orders tables, and the `OrdersDS` data source runs out of connections on `orders_ms1` and `orders_ms2`. On average, 3.889 requests wait for a connection over six hours, against 0 on the previous days. The relationships chart peaks at about 20 waiting requests, and the breakdown marks the Order Management application as a spike. The requests stop waiting about 50 minutes later, when the batch job releases its locks. Add an [SLA](https://docs.germainux.com/analytics/slas.md) on this KPI to get an [alert](https://docs.germainux.com/automation/notifications.md) as soon as requests start to wait.

![Analysis screen for the WebLogic JDBC Waiting For Connection Current Count KPI, with an average of 3.889 waiting requests against 0.000 on the previous days, a peak of about 20 in the relationships chart, and Order Management marked as a spike](https://mintcdn.com/germain-ux/ES2SyPExMrRBE5X6/images/main/oracle-weblogic-monitoring/weblogic-jdbc-waiting-analysis.png?fit=max\&auto=format\&n=ES2SyPExMrRBE5X6\&q=85\&s=a500eac2c4501b19216906e59c8dad67)

Analysis of WebLogic JDBC Waiting For Connection Current Count - GermainUX

### Investigate a JMS Backlog

When messages stop moving through a queue, open the **WebLogic JMS Messages Current Count** KPI in the Analysis screen. The top row compares the average queue depth with the previous days, and the segmentation breakdown lists the servers whose destinations grew most. Then check **WebLogic JMS Consumers Current Count** for the same destination: a destination without consumers keeps growing.

In the example below, the fulfilment system is down and the `FulfilmentMDB` message-driven bean is suspended. `OrderQueue` has no consumers on either server for 100 minutes, and the messages pile up. The average depth is 118.111 messages over six hours, against 4.943 on the previous days, and the relationships chart peaks at about 400 messages. The breakdown marks both servers as spikes, **wls-01** with 121.861 messages and **wls-02** with 114.361. The queue drains once the consumers come back.

![Analysis screen for the WebLogic JMS Messages Current Count KPI, with an average of 118.111 messages up more than 999% on the previous days, a peak of about 400 in the relationships chart, and wls-01 and wls-02 marked as spikes](https://mintcdn.com/germain-ux/ES2SyPExMrRBE5X6/images/main/oracle-weblogic-monitoring/weblogic-jms-messages-analysis.png?fit=max\&auto=format\&n=ES2SyPExMrRBE5X6\&q=85\&s=70aa11346fa0cc2f1c083b737fa2ddea)

Analysis of WebLogic JMS Messages Current Count - GermainUX

### Investigate a Failed Managed Server

When a managed server stops serving requests, open the **WebLogic Server State** KPI in the Analysis screen. Each reading is named after the state the server reports, so the segmentation breakdown lists the states that changed most. The top row compares the average with the previous days and shows the hourly trend.

In the example below, `orders_ms1` runs out of memory during a nightly export, fails, and Node Manager restarts it. The average state is 97.101% over six hours, against 100.000% on the previous days. The monitor records 69 readings instead of 72, because `orders_ms1` doesn't answer while it's down. The breakdown marks `ADMIN`, a state `orders_ms1` reports on its way back, as new and as an outlier. The state returns to 100% once the server is `RUNNING` again.

![Analysis screen for the WebLogic Server State KPI, with an average of 97.101% against 100.000% on the previous days, a dip in the hourly trend, and the ADMIN state marked as new and as an outlier](https://mintcdn.com/germain-ux/ES2SyPExMrRBE5X6/images/main/oracle-weblogic-monitoring/weblogic-server-state-analysis.png?fit=max\&auto=format\&n=ES2SyPExMrRBE5X6\&q=85\&s=ce14a20dcd7c943dd2b9d5ab64d29a3f)

Analysis of WebLogic Server State - GermainUX

### Investigate a Suspended Data Source

When applications lose their database on every server at once, open the **WebLogic JDBC State** KPI in the Analysis screen. The KPI is `100` while a data source is running and `0` otherwise, so the average drops as soon as one stops. The top row compares the average with the previous days and shows the hourly trend, and the relationships chart shows when the data source stopped and came back.

In the example below, the database fails over, and WebLogic suspends `OrdersDS` on `orders_ms1` and `orders_ms2` for about half an hour. The average state is 90.000% over five hours, against 100.000% on the previous days, and the relationships chart dips to 50%. The breakdown finds no leading factor, because the data source stops on both servers at the same time. The state returns to 100% once `OrdersDS` runs again. Add an [SLA](https://docs.germainux.com/analytics/slas.md) on this KPI to get an [alert](https://docs.germainux.com/automation/notifications.md) when a data source stops running.

![Analysis screen for the WebLogic JDBC State KPI, with an average of 90.000% against 100.000% on the previous days, a dip to 50% in the relationships chart, and no leading factor in the segmentation breakdown](https://mintcdn.com/germain-ux/ES2SyPExMrRBE5X6/images/main/oracle-weblogic-monitoring/weblogic-jdbc-state-analysis.png?fit=max\&auto=format\&n=ES2SyPExMrRBE5X6\&q=85\&s=75a09be7055a81610ed7c396c387d410)

Analysis of WebLogic JDBC State - GermainUX

### SLAs and Alerts

**WebLogic Server State** and **WebLogic Server Health State** come with a default [SLA](https://docs.germainux.com/analytics/slas.md) that is breached when a server isn't `RUNNING` or doesn't report `HEALTH_OK`. Add SLAs on other KPIs, such as stuck threads or requests waiting for a connection, and get an [alert](https://docs.germainux.com/automation/notifications.md) by email, SMS, Slack or Teams when one is breached.

### Automation

When an SLA is breached, an [automated action](https://docs.germainux.com/automation/automated-actions.md) can run a diagnostic script, such as a thread dump, call an HTTP endpoint or open an incident.

### Correlation with Other Technologies

[Correlate](https://docs.germainux.com/analytics/correlation-and-tracing.md) WebLogic data with the [Oracle Database](https://docs.germainux.com/integrations/oracle-db-observability.md) behind your data sources and with the browser sessions of your users, to follow a slow page to the pool or queue that caused it.

## How It Works

WebLogic Server
Remote JMX
JMX WebLogic Monitor
KPIs
Alerts

| Component | What it does |
| - | - |
| **JMX WebLogic Monitor** | Runs on a GermainUX Engine and connects to the runtime MBean server of one WebLogic Server on a schedule. It reads the thread pool, JDBC data source, JMS destination, JTA, server state and health, servlet and work manager MBeans. |
| **WebLogic rules** | Turn each reading into a fact named after the server, data source, destination, servlet or work manager it belongs to |

Each server has its own runtime MBean server, so you deploy one monitor for each server you want to watch, including managed servers. The host of the URI becomes the system name, which is how the KPIs and SLAs tell the servers apart. Counters such as transactions, received messages and servlet invocations run since the server started, as WebLogic reports them.

## Before You Start

* A [GermainUX Engine](https://docs.germainux.com/deploy/germain-ux-engine.md) can reach the listen port of every WebLogic server you monitor.
* You know the JMX service URL of the runtime MBean server of each WebLogic server.
* You have a WebLogic user for the monitor, for example one in the `Monitors` group, which has read-only access to the MBeans.
* Firewalls allow the Engine to reach the listen ports.

## Deploy

**1. Open the Java Monitor Deployment wizard**

In the left menu, go to **Settings > Wizards**. On the **Java Monitor Deployment** card, click **Add**.

**2. Choose the WebLogic monitor**

On the **Monitoring** step, fill in the fields, and then click **Next**.

| Field | Value |
| - | - |
| **Component Type** | **JMX WebLogic Monitor** |
| **Monitored Application** | The application to file the data under, for example `Order Management` |
| **Credentials** | The WebLogic user name and password for the monitor |

![Java Monitor Deployment wizard on the Monitoring step, with JMX WebLogic Monitor selected as the Component Type](https://mintcdn.com/germain-ux/ES2SyPExMrRBE5X6/images/main/oracle-weblogic-monitoring/java-monitor-deployment-weblogic.png?fit=max\&auto=format\&n=ES2SyPExMrRBE5X6\&q=85\&s=1451606cb3ecda0af7cb9e2cca27474b)

Java Monitor Deployment Wizard, Monitoring Step - GermainUX

**3. Connect to the server**

On the **Connection** step, select or create the **URI** that holds the JMX service URL of the server's runtime MBean server, and then click **Next**. Each managed server has its own listen port, so each one needs its own URI. Create URIs under **Settings > Data Sources**.

**4. Deploy it to the Engine**

On the **Deployment** step, enter a **Monitor Name**, such as `WebLogic orders_ms1`, and select the **Monitoring Node** and Engine. Set the schedule: the default, `0 0 * * * *`, runs once an hour, and `0 */5 * * * *` reads the server every 5 minutes. Finish the wizard.

**5. Repeat for the other servers**

Run the wizard once for each WebLogic server you want to monitor.

## Validate

**1. Wait for the first run**

The monitor reads the server at its next scheduled time, for example within 5 minutes with `0 */5 * * * *`.

**2. Open the WebLogic dashboard**

In the left menu, go to **Dashboards > All**, and then open **Weblogic Overview**. The thread charts show data for each server you deployed.

**3. Check server state**

The **WebLogic Server State** table lists each server as `RUNNING`, and **WebLogic Server Health State** as `HEALTH_OK`.

## Troubleshooting

> [accordion] No data appears for a server
>
> Check that the Engine can open a connection to the server's listen port, and that the host and port in the URI match the server. A managed server has its own listen port, different from the Administration Server's.

> [accordion] The connection fails with an authentication error
>
> The user name or password in **Credentials** is wrong, or the user isn't allowed to read MBeans. Use a user in the `Monitors` or `Administrators` group.

> [accordion] JDBC or JMS tables are empty
>
> The server has no JDBC data source or JMS destination deployed to it. The monitor only reads the resources that are targeted to the server it connects to.

## Security and Privacy

Oracle WebLogic monitoring data includes:

* **System data**: the host names of the WebLogic servers and the names of the servers
* **Application data**: the names of your applications, web modules, servlets, data sources, JMS destinations and work managers

GermainUX reads counts, sizes, times and states only. It doesn't read the messages in JMS destinations or the data your applications process.

To mask, anonymize or exclude this data, see [Data Privacy](https://docs.germainux.com/management/compliance-privacy-and-security/data-privacy.md).

## KPIs

| Group | KPI | What it holds |
| - | - | - |
| **Threads** | **WebLogic Total Execute Threads** | Threads in the execute thread pool |
| | **WebLogic Idle Execute Threads** | Idle threads ready to take new work, without standby and stuck threads |
| | **WebLogic Standby Threads** | Threads in standby, kept out of the active pool |
| | **WebLogic Hogging Threads** | Threads held by a request right now, which become stuck after the configured timeout |
| | **WebLogic Stuck Threads** | Threads declared stuck |
| **JDBC** | **WebLogic JDBC State** | `100` when the data source is running, `0` otherwise |
| | **WebLogic JDBC Curr Capacity** | Connections in the data source's pool |
| | **WebLogic JDBC Active Connections Current Count** | Connections in use by applications |
| | **WebLogic JDBC Active Connections Average Count** | Average number of connections in use |
| | **WebLogic JDBC Active Connections High Count** | Highest number of connections in use since the data source started |
| | **WebLogic JDBC Num Available** | Idle connections available to applications |
| | **WebLogic JDBC Num Unavailable** | Connections in use or being tested |
| | **WebLogic JDBC Leaked Connection Count** | Connections that were reserved and never closed |
| | **WebLogic JDBC Waiting For Connection Current Count** | Requests waiting for a connection |
| | **WebLogic JDBC Waiting For Connection Failure Total** | Requests that waited and failed to get a connection |
| **JMS** | **WebLogic JMS Messages Current Count** | Messages in the destination, without pending messages |
| | **WebLogic JMS Messages Pending Count** | Messages sent or received in a transaction that isn't committed or acknowledged yet |
| | **WebLogic JMS Messages Received Count** | Messages received by the destination |
| | **WebLogic JMS Consumers Current Count** | Consumers on the destination |
| **Transactions** | **WebLogic JTA Transaction Total Count** | Transactions processed since the server started |
| | **WebLogic JTA Transaction Committed Total Count** | Transactions committed since the server started |
| | **WebLogic JTA Transaction Rolled Back Total Count** | Transactions rolled back since the server started |
| **Server** | **WebLogic Server State** | `100` when the server is `RUNNING`, `0` otherwise |
| | **WebLogic Server Health State** | `100` when the server reports `HEALTH_OK`, `0` otherwise |
| **Servlets** | **WebLogic Servlet Invocation Total Count** | Invocations of each servlet |
| | **WebLogic Servlet Execution Time Low** | Shortest execution time of each servlet, in milliseconds |
| | **WebLogic Servlet Execution Time High** | Longest execution time of each servlet, in milliseconds |
| | **WebLogic Servlet Execution Time Average** | Average execution time of each servlet, in milliseconds |
| | **WebLogic Servlet Execution Time Total** | Total execution time of each servlet, in milliseconds |
| **Work managers** | **WebLogic Work Manager Completed Requests** | Requests completed by each work manager |
| | **WebLogic Work Manager Pending Requests** | Requests waiting in each work manager |

**WebLogic Server State** and **WebLogic Server Health State** have a default SLA: OK at `100` or higher, per server host. The other KPIs have no default SLA. Add the thresholds you need. See [KPIs](https://docs.germainux.com/analytics/kpis.md) and [SLAs](https://docs.germainux.com/analytics/slas.md).

## Related Documentation

> [card] [Java Monitoring](https://docs.germainux.com/integrations/java-monitoring.md)
>
> JVM metrics over JMX

> [card] [Oracle DB Observability](https://docs.germainux.com/integrations/oracle-db-observability.md)
>
> The database behind your data sources

> [card] [Automation](https://docs.germainux.com/automation.md)
>
> More Automation Features

## Get Help

The GermainUX team can help you monitor other WebLogic MBeans, such as clusters, EJB pools or the Administration Server's domain runtime.

> [card] [Contact GermainUX Support](https://docs.germainux.com/getting-started/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] Can't Find What You Need?
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.