RESTful WebLogic Monitoring of Servers, Applications, JDBC and JMS with Jolokia

[This posting will be a part of my upcoming WebLogic 12c book]

This article is part II of III. Make sure you read part I explaining the basics of monitoring WebLogic with WLST, the WebLogic 12c REST-ful management API and the open source framework Jolokia.

There will be a part III in a few of days, explaining how to use j4psh with WebLogic. j4psh is a JMX shell that resembles WLST in interactive mode but includes features such as syntax highlighting and tab-completion of commands and MBean names. j4psh is highly useful to interactively find out the correct MBean names used for the requests below.

WebLogic with Jolokia

Did you ever wonder how to retrieve the configuration values for a WebLogic managed server, runtime data of a JDBC connection pool or the number of messages in a particular JMS queue with a fast and simple HTTP GET?

The examples show typical use cases for monitoring a WebLogic domain with the following configuration:

– Admin server running at localhost:7001
– Managed server with name surf1 running at localhost:7003
– JDBC datasource with the name emergencyDB and associated connection pool (target set to surf1)
– JMS configuration with a JMS server surfJMS running on managed server surf1, a module surfJMSModule containing a queue name jms/ShippingRequestQueue (target of JMS server is surf1, JMS module subdeployment set to surfJMS)
– A deployment of a web service with the name SubmitOrder and target AdminServer and surf1.

An installation of Jolokia with target set to all server of the domain is recommended to follow the examples in this part.


General: List Configuration Details of Managed Server with Name surf1

Note, that without the ?ignoreErrors=true parameter the request would fail with an “NoAccessRuntimeException” because you cannot access the SSL keystore passphrases without proper authentication. Authentication is easily possible, but beyond of the scope of this article.

Deployment: List all Deployments

Deployment: List Deployments Details for an Application with the Name SubmitOrder

JDBC Data Source: Retrieve Settings for emergencyDB Data Source with Target Managed Server surf1 Running at localhost:7003

JDBC Connection Pool: Find all JMS Servers with Target set to Managed Server Running at localhost:7003

which returns the JMS server surfJMS:

JMS: Find all JMS Servers with Target set to Managed Server Running at localhost:7003

which returns the JMS server surfJMS:

JMS: Runtime Properties for a Particular Queue

Request the MessagesCurrentCount, MessagesHighCount and MessagesReceivedCount for a queue with the name jms/ShippingRequestQueue (note the “!” is used in the URL to escape the “/” character in the queue name) in a JMS module with the name surfJMSModule (note that JMS module and queue name are typically separated in the MBean Name attribute with a “!” which has to be escaped by another “!”).

which returns the following JSON structure.

The output for the queue monitoring shows that there was a total of 3 messages sent, with a maximum of 1 in the queue (because of a deployed receiver retrieving the messages immediately) and currently 0 message in the queue.



  1. Good day,

    Thank you for the information on Jolokia, I have successfully used it to retrieve JMS queue statistics from Weblogic 12.1.1 using Scala and the Jolokia JVM Agent.

    What I would like to do is pause and resume the queues which I have successfully done via Java and the Weblogic JMX runtime objects. So what I probably need to do is get Jolokia JVM Agent to login / register with Weblogic runtime but I am unsure if this is possible.

    Mark P Ashworth

  2. @Mark:

    I haven’t done it yet with Jolokia.

    Using WLST will be easiest for the job, after changing to serverRuntime(),
    1. cd() to the queue in JMSRuntime
    2. cmo.pauseConsumption()

    So try executing pauseConsumption() with Jolokia exec.
    You are lucky it’s on a runtime MBean so at least you can avoid the WLST startEdit(), set(), save(), activate() sequence.

    For authentication check the Jolokia docs, it is provided already in the Jolokia .war file you just have to remove some comments.

    let me know if it works!



  3. @Frank

    I downloaded the jolokia-1.1.1.war and configured it to use the Weblogic administrative role and then was able to perform the pauseConsumption and resumeConsumption operations on the JMSDestinationRuntime MBean.

    Thanks it worked like charm 🙂

  4. Hi Mark,

    brilliant, thanks for letting me know!

    have a great weekend,



  1. […] part II of this posting with examples showing how to use Jolokia to retrieve monitoring values for servers, JDBC and […]

  2. […] Management service vs. open source Jolokia discussion (based on older postings here and here) can be found in my WebLogic […]

Speak Your Mind