blob: dad6b60ad096f47a425adc8b7596653d07400c0c [file] [log] [blame]
// Do not edit directly!
// This file was generated by camel-quarkus-maven-plugin:update-extension-doc-page
[id="extensions-management"]
= Management
:linkattrs:
:cq-artifact-id: camel-quarkus-management
:cq-native-supported: true
:cq-status: Stable
:cq-status-deprecation: Stable
:cq-description: JMX management strategy and associated managed resources.
:cq-deprecated: false
:cq-jvm-since: 1.1.0
:cq-native-since: 3.2.0
ifeval::[{doc-show-badges} == true]
[.badges]
[.badge-key]##JVM since##[.badge-supported]##1.1.0## [.badge-key]##Native since##[.badge-supported]##3.2.0##
endif::[]
JMX management strategy and associated managed resources.
[id="extensions-management-maven-coordinates"]
== Maven coordinates
https://{link-quarkus-code-generator}/?extension-search=camel-quarkus-management[Create a new project with this extension on {link-quarkus-code-generator}, window="_blank"]
Or add the coordinates to your existing project:
[source,xml]
----
<dependency>
<groupId>org.apache.camel.quarkus</groupId>
<artifactId>camel-quarkus-management</artifactId>
</dependency>
----
ifeval::[{doc-show-user-guide-link} == true]
Check the xref:user-guide/index.adoc[User guide] for more information about writing Camel Quarkus applications.
endif::[]
[id="extensions-management-usage"]
== Usage
For information on using Managed Beans in Camel, consult the xref:manual::jmx.adoc[JMX section of the Camel Manual].
[id="extensions-management-usage-enabling-and-disabling-jmx"]
=== Enabling and Disabling JMX
JMX can be enabled or disabled in Camel-Quarkus by any of the following methods:
. Adding or removing the `camel-quarkus-management` extension.
. Setting the `camel.main.jmxEnabled` configuration property to a boolean value.
. Setting the system property `-Dorg.apache.camel.jmx.disabled` to a boolean value.
[id="extensions-management-usage-native-mode"]
=== Native mode
**Experimental** JMX support was added for native executables in GraalVM for JDK 17/20 / Mandrel 23.0. You can enable this feature by
adding the following configuration property to `application.properties`.
[source,properties]
----
quarkus.native.monitoring=jmxserver
----
If you want the native application to be discoverable by tools such as JConsole and VisualVM, append the `jvmstat` option to the above mentioned configuration.
For more information, refer to the https://quarkus.io/guides/building-native-image#using-monitoring-options[Quarkus native guide].