Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove support for Jolokia

Browse Source 
Closes gh-28704
This commit is contained in:
Andy Wilkinson
2021-11-16 14:54:34 +00:00
parent 79b53e3562
commit 85f9949513
14 changed files with 55 additions and 462 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/jmx.adoc
View File

@@ -52,57 +52,3 @@ If you do not want to expose endpoints over JMX, you can set the configprop:mana
exposure:
exclude: "*"
----
[[actuator.jmx.jolokia]]
=== Using Jolokia for JMX over HTTP
Jolokia is a JMX-HTTP bridge that provides an alternative method of accessing JMX beans.
To use Jolokia, include a dependency to `org.jolokia:jolokia-core`.
For example, with Maven, you would add the following dependency:
[source,xml,indent=0,subs="verbatim"]
----
<dependency>
<groupId>org.jolokia</groupId>
<artifactId>jolokia-core</artifactId>
</dependency>
----
You can then expose the Jolokia endpoint by adding `jolokia` or `*` to the configprop: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 is not available in a WebFlux application.
[[actuator.jmx.jolokia.customizing]]
==== Customizing Jolokia
Jolokia has a number of settings that you would traditionally configure by setting servlet parameters.
With Spring Boot, you can use your `application.properties` file.
To do so, prefix the parameter with `management.endpoint.jolokia.config.`, as the following example shows:
[source,yaml,indent=0,subs="verbatim",configprops,configblocks]
----
management:
endpoint:
jolokia:
config:
debug: true
----
[[actuator.jmx.jolokia.disabling]]
==== Disabling Jolokia
If you use Jolokia but do not want Spring Boot to configure it, set the configprop:management.endpoint.jolokia.enabled[] property to `false`, as follows:
[source,yaml,indent=0,subs="verbatim",configprops,configblocks]
----
management:
endpoint:
jolokia:
enabled: false
----