3.0.0-M5: JMX Endpoint Exposure

From the Release Notes

By default, only the health endpoint is now exposed over JMX, to align with the default web endpoint exposure. This can be changed by configuring the management.endpoints.jmx.exposure.include and management.endpoints.jmx.exposure.exclude properties.

What needs to be done

To guarantee that JMX endpoint exposure is exactly the same as prior to 3.0 the settings in 2.7 should be restored and the user should be warned about the implications and how to secure JMX endpoints.

Report

Condition

Application is a Spring Boot 3.0.0 application and management.endpoints.jmx.exposure.include is not set.

Section

By default, only the health endpoint is now exposed over JMX, to align with the default web endpoint exposure. This can be changed by configuring the management.endpoints.jmx.exposure.include and management.endpoints.jmx.exposure.exclude properties. As Spring Boot Migrator can’t tell if the JMX endpoints provided in 2.7 are used, the recipe will restore the defaults as in 2.7 by setting management.endpoints.jmx.exposure.include=*. This exposes all management endpoints over JMX. To provide only required information over JMX we strongly recommend to configure the management.endpoints.jmx.exposure.include property to your specific needs and only expose required JMX endpoints. Please consult the reference documentation Spring Boot 3.0.0-M5 or after 3.0.0 is GA: Spring Boot 3.0.0

Recipe

Condition

Application is a Spring Boot 3.0.0 application and management.endpoints.jmx.exposure.include is not set.

Action

• Set management.endpoints.jmx.exposure.include=* in application.properties

[fabapp2]

Hi @ishu-thakur Thanks for asking these questions! Your questions highlighted more missing bits in #446 I will answer your questions there, hoping it’s helpful for others.

[DevPJ9]

Hello @fabapp2.I know @ishu-thakur and will be able to sync with him. Thanks for your suggestion and support.