Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Jetty/Feature/JMX"
| (17 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{Jetty Feature | {{Jetty Feature | ||
| introduction = | | introduction = | ||
| − | + | ||
| + | {{Jetty Redirect|http://www.eclipse.org/jetty/documentation/current/jmx-chapter.html}} | ||
| + | |||
| + | [http://java.sun.com/products/JavaManagement/ Java Management Extensions] (JMX) API is a standard API for management and monitoring of resources such as applications, devices, services, and the Java virtual machine. The JMX technology was developed through the Java Community Process. | ||
Typical uses of the JMX technology include: | Typical uses of the JMX technology include: | ||
| − | |||
* Consulting and changing application configuration. | * Consulting and changing application configuration. | ||
* Accumulating statistics about application behavior and making them available. | * Accumulating statistics about application behavior and making them available. | ||
| − | * Notifying of state changes and erroneous conditions. | + | * Notifying of state changes and erroneous conditions. |
The JMX API includes remote access, so a remote management program can interact with a running application for these purposes. | The JMX API includes remote access, so a remote management program can interact with a running application for these purposes. | ||
| + | |||
| body = | | body = | ||
| + | Jetty JMX integration can be configured using etc/jetty-jmx.xml configuration file. See [[Jetty/Tutorial/JMX|Jetty JMX tutorial]] for instructions on how to configure Jetty JMX integration. | ||
| − | + | In order to monitor an application using JMX, the following steps have to be performed: | |
| + | # Application should instantiate an MBean container. | ||
| + | # Objects have to be instrumented to be MBeans. | ||
| + | # MBeans need to be accessed by JMX agents. | ||
| − | The | + | Jetty JMX integration uses platform MBean server implementation provided by Java VM. The integration is based on the ObjectMBean implementation of DynamicMBean. This implementation allows an arbitrary POJO to be wrapped in an MBean and for meta data to be provided by [http://dev.eclipse.org/viewcvs/index.cgi/jetty/trunk/jetty-jmx/src/main/resources/org/eclipse/jetty/?root=RT_Jetty properties files]. |
| − | + | The creation of MBeans is coordinated by the MBeanContainer implementation of the Container.Listener interface. The Jetty Server and it's components use a [http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/util/component/Container.html Container] to maintain a containment tree of components and to support notification of changes to that tree. The MBeanContainer class listens for Container events and creates and destroys MBeans as required to wrap all Jetty components. | |
| − | + | MBeans published by Jetty can be accessed both through built-in Java VM connector via JConsole, or by registering a remote JMX connector and using a remote JMX agent to monitor Jetty. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| more = | | more = | ||
| − | See [[Jetty/ | + | * See [[Jetty/Tutorial/JMX|Jetty JMX tutorial]] for instructions on how to configure Jetty JMX integration. |
| + | * The [http://code.google.com/p/jminix/ JMiniX] web consoles for JMX beans. | ||
| categories = [[Category:Jetty Feature]] | | categories = [[Category:Jetty Feature]] | ||
}} | }} | ||
Latest revision as of 15:05, 26 April 2013
Introduction
THIS IS NOT THE DOCUMENTATION YOU ARE LOOKING FOR!!!!!
All development and stable releases are being performed with Jetty 9 and Jetty 10.
This wiki is now officially out of date and all content has been moved to the Jetty Documentation Hub
Java Management Extensions (JMX) API is a standard API for management and monitoring of resources such as applications, devices, services, and the Java virtual machine. The JMX technology was developed through the Java Community Process.
Typical uses of the JMX technology include:
- Consulting and changing application configuration.
- Accumulating statistics about application behavior and making them available.
- Notifying of state changes and erroneous conditions.
The JMX API includes remote access, so a remote management program can interact with a running application for these purposes.
Feature
Jetty JMX integration can be configured using etc/jetty-jmx.xml configuration file. See Jetty JMX tutorial for instructions on how to configure Jetty JMX integration.
In order to monitor an application using JMX, the following steps have to be performed:
- Application should instantiate an MBean container.
- Objects have to be instrumented to be MBeans.
- MBeans need to be accessed by JMX agents.
Jetty JMX integration uses platform MBean server implementation provided by Java VM. The integration is based on the ObjectMBean implementation of DynamicMBean. This implementation allows an arbitrary POJO to be wrapped in an MBean and for meta data to be provided by properties files.
The creation of MBeans is coordinated by the MBeanContainer implementation of the Container.Listener interface. The Jetty Server and it's components use a Container to maintain a containment tree of components and to support notification of changes to that tree. The MBeanContainer class listens for Container events and creates and destroys MBeans as required to wrap all Jetty components.
MBeans published by Jetty can be accessed both through built-in Java VM connector via JConsole, or by registering a remote JMX connector and using a remote JMX agent to monitor Jetty.
Additional Resources
- See Jetty JMX tutorial for instructions on how to configure Jetty JMX integration.
- The JMiniX web consoles for JMX beans.