Monitor with JMX

Kaazing Gateway supports Java Management Extension (JMX) access through any JMX-compliant console, such as Java’s built-in Java Management and Monitoring Console (JConsole) or MC4J, or through any program that supports communication using the JMX protocol. The Gateway supports a management.jmx service to allow JMX-compliant applications to monitor current Gateway service and session state and operate on individual sessions. See the Service Reference for information about the JMX management service (management.jmx).

Before You Begin

This procedure is part of Monitor the Gateway:

  1. Introduction to Monitoring Kaazing Gateway
  2. Secure Kaazing Gateway Monitoring
  3. Monitor a Gateway or Gateway cluster
    • Monitor with JMX
  4. Troubleshoot the Gateway

To Monitor with JMX

  1. Stop the Gateway if it is running.
  2. Open the Gateway configuration file, GATEWAY_HOME/gateway-config.xml.
  3. Add the management.jmx service as defined in management.jmx.
  4. Start the Gateway as described in Setting Up the Gateway.

    Note: To connect to a JMX service on a Gateway running on an EC2 instance, configure the GATEWAY_OPTS environment variable with the -Djava.rmi.server.hostname property set to the IP address or hostname being used in the RMI registry. For example, GATEWAY_OPTS="-Xmx512m See the topic Configure Kaazing Gateway Using the GATEWAY_OPTS Environment Variable for more information.

  5. Ensure secure monitoring by verifying that your configuration specifies a security realm name and an authorization constraint. This is set up automatically if you use the default Gateway configuration. See Secure Kaazing Gateway Monitoring for more information.
  6. Start your favorite Java monitoring console or application. This documentation uses JConsole for its examples.
  7. Select the local process, for example org.kaazing.gateway.server.Main (as shown in the following screenshot), then click Connect. (For Windows, the local process name is org.kaazing.gateway.server.WindowsMain.)


    Figure: Monitoring the Local Process with JConsole


    • To connect to a remote process you must specify an address that uniquely represents the remote instance of the Gateway and provide the administrator’s user name and password (by default, admin/admin). If there are multiple instances of the Gateway on a remote server then JMX management is hosted on different ports.
    • For remote monitoring, ensure that you set the correct system properties when you start the Gateway (for example, For more information, see Monitoring and Management Using JMX Technology from Oracle.
    • Use the following syntax to access your local Gateway as a remote process (where hostname is the remote hostname): service:jmx:rmi://hostname/jndi/rmi://hostname:2020/jmxrmi
    • Password authentication over the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) is enabled by default in JMX. Consequently, you must have a digital certificate for the hostname of the Gateway in the keystore.db file used by the Gateway. In addition, access to port 2020 must be enabled in your network for the remote monitoring agent to connect to the Gateway. For information on how to create a certificate for the hostname of the Gateway, see Secure Network Traffic with the Gateway.
  8. JConsole displays information about the particular JVM process you just clicked on or entered.
  9. Click the MBeans tab.
  10. Expand the service that you want to monitor.

    For example, the following JConsole screenshot shows an expanded > service and expanded the echo node.

    JConsole session

    Figure: Viewing the Echo Service in JConsole

  11. Click one of the session IDs. The session data exposed by the MBeans displays. Here, you can examine the user sessions on the Gateway.

Get Started with JMX Monitoring

The steps in this section use the JConsole example from the previous section to demonstrate the procedure.

To Examine Available Sessions:

  1. Click the service that you want to examine.

    For example, in our running JConsole example, you would click the Echo service, as this is the service being used by the demo you started.

  2. Expand the connection.
  3. Expand the sessions node to view the session IDs.
  4. Select the session ID you want to manage. The following screenshot shows that you can manually manage the session, such as using the close() or the closeImmediately operation, to explicitly close the specific session:

    This screenshot shows the JConsole GUI displying the service > echo > ws://localhost:8001/echo > sessions > Operations path. Two operations are available under Operations: close and closeImmediately

    Figure: Subscribing to a Session in JConsole

Next Step

You have configured management with JMX for Kaazing Gateway.

See Also