Extended Monitoring Guide

  • Docs Home
  • Community Home
1. About
Prev Chapter 19. BEA WebLogic Application Server Next

1. About

WebLogicMonitor is a ZenPack that allows System Administrators to monitor a WebLogic Server. WebLogicMonitor uses the JMX Remote API and and accesses MBeans deployed within WebLogic that contain performance information about the components that are being managed. This performance information includes pool sizes for data sources (JDBC), threads, connections (JCA), queues (JMS), servlets, JSPs, Enterprise Java Beans (EJB), timer queues.

Throughput is also monitored when it is available. This metric is computed by WebLogic and is based on the number of messages moving through a queue at any given time. The throughput metric gives a good picture of the health of the messaging subsystem, which is commonly used throughout many enterprise applications. Stateless, Stateful, and Entity EJB performance metrics are monitored, as are message driven bean performance.

Security realms are also monitored for potential denial of service attacks. This includes recording of authentication failures, broken out by valid accounts, invalid accounts, and accounts that are currently locked out. Application specific realms can be monitored by customizing the built in WebLogic default realm.

1.1. Overall Application Server Vitals

  • Number of total and active JMS connections and servers

  • Overall number of JTA transactions that are rolled back or abandoned

  • JTA transactions rolled back due to system, application, or resource issues

  • Number of JTA rollbacks that timeout

  • Active and committed JTA transaction count

  • Timer exceptions, executions, and scheduled triggers

  • User accounts that are locked and unlocked

  • Authentication failures against locked accounts and non-existent accounts

  • Total sockets opened, and the current number of open sockets

  • JVM Mark/Sweep and Copy garbage collector execution counts

  • Number of JVM daemon threads

  • JVM Heap/Non-Heap used and committed memory

1.2. Entity EJB, Message Driven Bean (MDB), and Session EJB Subsystem Metrics

  • Rollback and commit count on a per-EJB basis

  • Bean pool accesses, cache hits, and cache misses

  • Number of Beans in use, idle, and destroyed

  • Number of activations and passivations

1.3. Data Pool (JDBC) metrics

  • Leaked, Total, and Active connections

  • Number of requests waiting for a connection

  • Number of reconnect failures

1.4. Queue (JMS) Metrics

  • Bytes received, currently active, and pending in the queue

  • Number of queue consumers

  • Number of current, pending, and receives messages

Prev Up Next
Chapter 19. BEA WebLogic Application Server Home 2. Prerequisites