JMX Access To Standalone EAP 7: Difference between revisions
Jump to navigation
Jump to search
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:51, 18 October 2016
External
- How to access MBeanServerConnection from remote JMX Client in JBoss EAP 7 https://access.redhat.com/solutions/2604501
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.