@@ -125,9 +125,6 @@ If you are using Spring MVC, the following additional endpoints can also be used
125
125
|`heapdump`
126
126
|Returns a GZip compressed `hprof` heap dump file.
127
127
128
- |`jolokia`
129
- |Exposes JMX beans over HTTP (when Jolokia is on the classpath).
130
-
131
128
|`logfile`
132
129
|Returns the contents of the logfile (if `logging.file` or `logging.path` properties have
133
130
been set). Supports the use of the HTTP `Range` header to retrieve part of the log file's
@@ -802,31 +799,31 @@ using Maven you would add the following:
802
799
</dependency>
803
800
----
804
801
805
- Jolokia can then be accessed using `/jolokia` on your management HTTP server.
802
+ Jolokia can then be accessed using `/application/ jolokia` on your management HTTP server.
806
803
807
804
808
805
809
806
[[production-ready-customizing-jolokia]]
810
807
==== Customizing Jolokia
811
808
Jolokia has a number of settings that you would traditionally configure using servlet
812
809
parameters. With Spring Boot you can use your `application.properties`, simply prefix the
813
- parameter with `jolokia.config.`:
810
+ parameter with `management. jolokia.config.`:
814
811
815
812
[source,properties,indent=0]
816
813
----
817
- jolokia.config.debug=true
814
+ management. jolokia.config.debug=true
818
815
----
819
816
820
817
821
818
822
819
[[production-ready-disabling-jolokia]]
823
820
==== Disabling Jolokia
824
821
If you are using Jolokia but you don't want Spring Boot to configure it, simply set the
825
- `endpoints .jolokia.enabled` property to `false`:
822
+ `management .jolokia.enabled` property to `false`:
826
823
827
824
[source,properties,indent=0]
828
825
----
829
- endpoints .jolokia.enabled=false
826
+ management .jolokia.enabled=false
830
827
----
831
828
832
829
0 commit comments