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"
| Line 11: | Line 11: | ||
| body = | | body = | ||
| − | + | ... | |
| more = | | more = | ||
| − | See [[Jetty/ | + | See [[Jetty/Tutorial/JMX|Jetty JMX tutorial]] for instructions on how to configure Jetty JMX integration. |
| categories = [[Category:Jetty Feature]] | | categories = [[Category:Jetty Feature]] | ||
}} | }} | ||
Revision as of 20:49, 22 December 2009
Introduction
The 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
...
Additional Resources
See Jetty JMX tutorial for instructions on how to configure Jetty JMX integration.