Skip to content

Commit 708ca06

Browse files
committed
Clarify that Spring Boot uses the platform MBeanServer by default
Closes gh-15728
1 parent c6f5719 commit 708ca06

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6477,9 +6477,13 @@ If that property is not set, the auto-configuration falls back to the value of
64776477
[[boot-features-jmx]]
64786478
== Monitoring and Management over JMX
64796479
Java Management Extensions (JMX) provide a standard mechanism to monitor and manage
6480-
applications. By default, Spring Boot creates an `MBeanServer` bean with an ID of
6481-
`mbeanServer` and exposes any of your beans that are annotated with Spring JMX
6482-
annotations (`@ManagedResource`, `@ManagedAttribute`, or `@ManagedOperation`).
6480+
applications. Spring Boot exposes the most suitable `MBeanServer` as a bean with an ID of
6481+
`mbeanServer`. Any of your beans that are annotated with Spring JMX annotations (
6482+
`@ManagedResource`, `@ManagedAttribute`, or `@ManagedOperation`) are exposed to it.
6483+
6484+
If your platform provides a standard `MBeanServer`, Spring Boot will use that and default
6485+
to the VM `MBeanServer` if necessary. If all that fails, a new `MBeanServer` will be
6486+
created.
64836487

64846488
See the
64856489
{sc-spring-boot-autoconfigure}/jmx/JmxAutoConfiguration.{sc-ext}[`JmxAutoConfiguration`]

0 commit comments

Comments
 (0)