From c98fe51914f85cf8d2444f20e15cd70a6f8b4bbb Mon Sep 17 00:00:00 2001 From: Madhura Bhave Date: Tue, 14 Apr 2020 16:45:31 -0700 Subject: [PATCH] Make it more obvious that Jolokia does not work with a WebFlux app Closes gh-20623 --- .../src/main/asciidoc/production-ready-features.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc index 085e6db43a..bed7aabfb8 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc @@ -1146,6 +1146,10 @@ For example, with Maven, you would add the following dependency: The Jolokia endpoint can then be exposed by adding `jolokia` or `*` to the `management.endpoints.web.exposure.include` property. You can then access it by using `/actuator/jolokia` on your management HTTP server. +NOTE: The Jolokia endpoint exposes Jolokia's servlet as an actuator endpoint. +As a result, it is specific to servlet environments such as Spring MVC and Jersey. +The endpoint will not be available in a WebFlux application. + [[production-ready-customizing-jolokia]]