From 708ca0636f9c8845623703d397c82a38cfbf1cb3 Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Thu, 17 Jan 2019 10:58:08 -0500 Subject: [PATCH] Clarify that Spring Boot uses the platform MBeanServer by default Closes gh-15728 --- .../src/main/asciidoc/spring-boot-features.adoc | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc index 8a85a429b14..17e6f7a8e4a 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc @@ -6477,9 +6477,13 @@ If that property is not set, the auto-configuration falls back to the value of [[boot-features-jmx]] == Monitoring and Management over JMX 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 -`mbeanServer` and exposes any of your beans that are annotated with Spring JMX -annotations (`@ManagedResource`, `@ManagedAttribute`, or `@ManagedOperation`). +applications. Spring Boot exposes the most suitable `MBeanServer` as a bean with an ID of +`mbeanServer`. Any of your beans that are annotated with Spring JMX annotations ( +`@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 {sc-spring-boot-autoconfigure}/jmx/JmxAutoConfiguration.{sc-ext}[`JmxAutoConfiguration`]