JMX Access to Standalone EAP 6: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:
* [[WildFly_and_JMX#Procedures|WildFly and JMX]]
* [[WildFly_and_JMX#Procedures|WildFly and JMX]]
* [[Remoting_WildFly_Subsystem_Concepts#Remoting_and_JMX_Access|WildFly Remoting Concepts]]
* [[Remoting_WildFly_Subsystem_Concepts#Remoting_and_JMX_Access|WildFly Remoting Concepts]]
=Overview=
JBoss Remoting provides the transport of the [[JSR 160 Java Management Extensions (JMX) Remote API|JSR-160 Java Management Extensions (JMX) Remote API]] compliant implementation of a [[JMXConnector]] that can be used by standard monitoring applications to access the JMX bus.

Revision as of 16:50, 18 October 2016

External

Internal

Overview

JBoss Remoting provides the transport of the JSR-160 Java Management Extensions (JMX) Remote API compliant implementation of a JMXConnector that can be used by standard monitoring applications to access the JMX bus.