Documentation forServer & Application Monitor

Oracle WebLogic (JMX)

This SAM template for Oracle WebLogic server statistics by using the JMX protocol. You can use the Orion agent for Linux or SNMP agentless to monitor.

This template was updated to support WebLogic 12.2.1.3.0 in SAM 2020.2. If you installed an earlier version of SAM, you can import the latest version of this template from THWACK.

To comply with Federal Information Processing Standards (FIPS), JMX monitoring is disabled when FIPS mode is enabled on the Orion server, starting in SAM 2020.2.

Prerequisites

Target servers support JMX queries. See Configure Java Virtual Machines for JMX monitoring in SAM.

Template configuration changes

The following settings in the component monitors should be changed from defaults:

  • This template is configured to send JMX requests on port 8686. For this Oracle WebLogic template, you should change the port to 7001.
  • The URL is set to /jmxrmi by default. For this template, set the URL to /jndi/weblogic.management.mbeanservers.runtime.
  • The JMX protocol default setting for this template is Remote Method Invocation (RMI). For this template, change the JMX protocol to Internet Inter-ORB Protocol (IIOP).

Credentials

Dependent upon JMX configuration.

Configurations for Orion agent for Linux

For JMX configurations, install and configure WebSphere per your Linux/Unix distribution. See the IBM Knowledge Center (© 2020 IBM Corp., available at https://www.ibm.com, obtained on January 10, 2020) for details.

The overall steps include:

  1. Install WebSphere and note the following details:
    • You may need to create an administrator account and a new package group.
    • During installation, turn off the secure storage option as this is not needed.
    • Make sure to select the Application Server during installation.
  2. Start and stop the WebSphere AppServer.
  3. Use a browser to access the WebSphere AppServer console at http://websphere-host:9060/ibm/console
    • You may need to open a port to 9060 on the Websphere host.
    • Use the credentials for the account created during installation.
  4. In the console, expose the JMX platform mbeans in the WebSphere AppServer by:
    1. Clicking Servers > Server Types > WebSphere application servers.
    2. Selecting the listed application server.
  5. Locate the Java and Process Management > Process definition. In the Generic JVM arguments dialog box, enter the following code:

    Djavax.management.builder.initial=

    Note: There is nothing after the = sign.

    Dcom.sun.management.jmxremote=true

    Dcom.sun.management.jmxremote.port=8686

    Dcom.sun.management.jmxremote.ssl=false

    Dcom.sun.management.jmxremote.authenticate=false

    Djava.rmi.server.hostname=localhost

  6. Restart the AppServer.

Component monitors

Component monitors without predetermined threshold values provide guidance such as "Use the lowest threshold possible" or "Use the highest threshold possible" to help you find an appropriate threshold for your environment. See Manage thresholds in SAM.

Classes Loaded Count

The number of classes that are currently loaded in the Java virtual machine.

Classes Total Loaded Count

The total number of classes that have been loaded since the Java virtual machine has started execution.

Classes Unloaded Count

The total number of classes unloaded since the Java virtual machine has started execution.

Memory Pending Final Count

The approximate number of objects for which finalization is pending.

Memory Heap Init Size (B)

The initial amount of memory in bytes that the Java virtual machine allocates; or -1 if undefined.

Memory Heap Used (B)

The amount of used memory in bytes. The amount of used memory in the returned memory usage is the amount of memory occupied by both live objects and garbage objects that have not been collected, if any.

Memory Heap Committed (B)

The amount of committed memory in bytes.

Memory Heap Max Size (B)

The maximum amount of memory in bytes that can be used; or -1 if undefined.

Memory Non Heap Init Size (B)

The initial amount of memory in bytes that the Java virtual machine allocates; or -1 if undefined.

Memory Non Heap Used (B)

The amount of used memory in bytes.

Memory Non Heap Committed (B)

The amount of committed memory in bytes.

Memory Non Heap Max Size (B)

The maximum amount of memory in bytes that can be used; or -1 if undefined.

Memory Garbage Collections Count

The approximate accumulated collection elapsed time in milliseconds.

Memory Garbage Collection Time (ms)

The approximate accumulated collection elapsed time in milliseconds.

Memory Pool Init Size (B)

The initial amount of memory (in bytes) that the Java virtual machine requests from the operating system for memory management during startup. The Java virtual machine may request additional memory from the operating system and may also release memory to the system over time. The value of init may be undefined.

Memory Pool Used (B)

The amount of memory currently used (in bytes).

Memory Pool Committed Size (B)

The amount of memory (in bytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used.

Memory Pool Max Size (B)

The maximum amount of memory (in bytes) that can be used for memory management. Its value may be undefined. The maximum amount of memory may change over time if defined. The amount of used and committed memory will always be less than or equal to max if max is defined. A memory allocation may fail if it attempts to increase the used memory such that used > committed even if used <= max would still be true (for example, when the system is low on virtual memory).

Memory Pool Peak Used (B)

The peak amount of memory currently used (in bytes).

Memory Pool Peak Committed (B)

The peak amount of memory (in bytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used.

Memory Pool Peak Max Size (B)

The maximum peak amount of memory (in bytes) that can be used for memory management. Its value may be undefined. The maximum amount of memory may change over time if defined. The amount of used and committed memory will always be less than or equal to max if max is defined. A memory allocation may fail if it attempts to increase the used memory such that used > committed even if used <= max would still be true (for example, when the system is low on virtual memory).

Threads Total Started Count

The total number of threads created and also started since the Java virtual machine started.

Current Thread Count

The current number of live threads including both daemon and non-daemon threads.

Current Thread Cpu Time

The total CPU time for the current thread in nanoseconds.

Current Thread User Time

The CPU time that the current thread has executed in user mode in nanoseconds.

Runtime Uptime (ms)

The uptime of the Java virtual machine in milliseconds.

Compiler Time (ms)

The approximate accumulated elapsed time (in milliseconds) spent in compilation.

JVM Runtime: Heap Free Current

The current amount of memory (in bytes) that is available in the JVM heap.

JVM Runtime: Heap Free Percent

The percentage of the maximum memory that is free.

JVM Runtime: Heap Size Current

The current size (in bytes) of the JVM heap.

JVM Runtime: Heap Size Max

The maximum free memory configured for this JVM.

JVM Runtime: Uptime

The number of milliseconds that the Virtual Machine has been running.

JTA Recovery Runtime: Initial Recovered Transactions

The total number of transactions that are recovered from the transaction log initially.

JTA Recovery Runtime: Recovered Transaction Completion Percent

The percentage of transactions that are recovered from the transaction log initially.

Server Security Runtime: Invalid Login Attempts

The total number of invalid logins that have been attempted on this server instance.

Server Security Runtime: Current Locked Users

The current number of locked users on this server instance.

Server Security Runtime: Login Attempts While Locked

The total number of invalid logins that have been attempted on this server instance while a user was locked.

Server Security Runtime: Unlocked Users

The total number of times a user of this server instance has been unlocked.

Server Security Runtime: User Lockout

The total number of user lockouts that have occurred on this server instance.

JTA Coordinator: Threads Constraint Runtime: Out Of Order Executions

The number of requests executed out of turn to satisfy this constraint.

JTA Coordinator: Threads Constraint Runtime: Current Wait Time

The last measured time a request had to wait for a thread. Only requests whose execution is needed to satisfy the constraint are considered.

JTA Coordinator: Threads Constraint Runtime: Executing Requests

The number of requests that are currently executing.

JTA Coordinator: Threads Constraint Runtime: Must Run

The number of requests that must be executed to satisfy the constraint.

JTA Coordinator: Threads Constraint Runtime: Pending Requests

The pending requests that are waiting for an available thread.

JTA Coordinator: Request Class: Pending Request

The number of requests waiting for a thread to become available. A request class represents a class of work. Work using the same request class shares the same priority.

JTA Coordinator: Work Manager: Pending Requests

The number of waiting requests in the queue of Work Manager.

JTA Runtime: Active Transactions

The number of active transactions on the server.

JTA Runtime: Total Transaction

The total number of transactions processed. This total includes all committed, rolled back, and heuristic transaction completions since the server was started.

JTA Runtime: Total Rolled Back Transactions

The number of transactions that were rolled back since the server was started.

User Lockout: Threads Constraint Runtime: Deferred Requests

The number of requests that are denied a thread for execution because the constraint is exceeded.

User Lockout: Threads Constraint Runtime: Executing Requests

The number of requests that are currently executing.

User Lockout: Work Manager: Pending Requests

The number of waiting requests in the queue.

User Lockout: Work Manager: Stuck Thread Count

The number of threads that are considered to be stuck on the basis of any stuck thread constraints.

WLS Admin Server: Allocated IO Buffer Bytes

The amount of off-heap (native) memory, in bytes, reserved for file store use.

WLS Admin Server: Allocated Window Buffer Bytes

The amount of off-heap (native) memory, in bytes, reserved for file store window buffer use.

WLS Admin Server: Object Count

The number of objects contained in the store.