WildFly and JMX

From NovaOrdis Knowledge Base
Revision as of 21:38, 7 July 2017 by Ovidiu (talk | contribs) (→‎Procedures)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Internal

Overview

Each JBoss instance has a JMX bus with various JMX MBeans deployed on it. The JMX MBeans expose management functionality, which can be used for monitoring or operations. For a JBoss instance running in standalone mode, there is just one JMX bus to access - the one of the standalone instance. However, for a JBoss instance running in domain mode, the JMX buses of a domain and host controller expose access to a different functionality than the JMX buses of the server nodes, and different procedures are required to access them.

Procedures

EAP 6 EAP 7 JDG 7
standalone mode instance JMX Access Procedure JMX Access Procedure
domain mode host controller JMX Access Procedure JMX Access Procedure
domain mode server node JMX Access Procedure JMX Access Procedure JMX Access Procedure

Programmatic JMX Access

The WildFly JMX bus can be accessed programmatically using standard JMX remoting API, as described in the Remote Access to a JMX Server section. novaordis-jmx is a library that provides a thin layer of functionality in top of the client-side JMX remoting API, with the intention to facilitate programmatic JMX access to a remote JMX bus. For a detailed discussion on how novaordis-jmx uses the JMX remoting API in conjunction with WildFly remoting JMX capabilities, see:

Accessing WildFly JMX Bus Remotely with novaordis-jmx