Commit cea6a79e authored by Stephane Nicoll's avatar Stephane Nicoll

Merge branch '2.1.x'

parents 33f2bd4d 708ca063
...@@ -6479,9 +6479,13 @@ If that property is not set, the auto-configuration falls back to the value of ...@@ -6479,9 +6479,13 @@ If that property is not set, the auto-configuration falls back to the value of
[[boot-features-jmx]] [[boot-features-jmx]]
== Monitoring and Management over JMX == Monitoring and Management over JMX
Java Management Extensions (JMX) provide a standard mechanism to monitor and manage Java Management Extensions (JMX) provide a standard mechanism to monitor and manage
applications. By default, Spring Boot creates an `MBeanServer` bean with an ID of applications. Spring Boot exposes the most suitable `MBeanServer` as a bean with an ID of
`mbeanServer` and exposes any of your beans that are annotated with Spring JMX `mbeanServer`. Any of your beans that are annotated with Spring JMX annotations (
annotations (`@ManagedResource`, `@ManagedAttribute`, or `@ManagedOperation`). `@ManagedResource`, `@ManagedAttribute`, or `@ManagedOperation`) are exposed to it.
If your platform provides a standard `MBeanServer`, Spring Boot will use that and default
to the VM `MBeanServer` if necessary. If all that fails, a new `MBeanServer` will be
created.
See the See the
{sc-spring-boot-autoconfigure}/jmx/JmxAutoConfiguration.{sc-ext}[`JmxAutoConfiguration`] {sc-spring-boot-autoconfigure}/jmx/JmxAutoConfiguration.{sc-ext}[`JmxAutoConfiguration`]
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment