JMX for all Java-based services should be enabled by default, so JVisualVM or any other tool could be attached without rebuilding the image.
The following options should be configured by envvars:
-Dcom.sun.management.jmxremote.authenticate with $SERVICE_JMX_DISABLED
-Djava.rmi.server.hostname with $SERVICE_JMX_DOMAIN
The following ports should be reserved for the service:
data-archiving-service - 8980
device-proxy-service - 8981
api-gateway - 9990
Actually JMX is enabled by default for api-gateway, so there is no need to do anything else. To attach JVisualVM to it, the jboss-client.jar should be added in the classpath and service:jmx:http-remoting-jmx:// should be used to provide the server address.
JMX for all Java-based services should be enabled by default, so JVisualVM or any other tool could be attached without rebuilding the image.
The following options should be configured by envvars:
-Dcom.sun.management.jmxremote.authenticatewith$SERVICE_JMX_DISABLED-Djava.rmi.server.hostnamewith$SERVICE_JMX_DOMAINThe following ports should be reserved for the service:
data-archiving-service-8980device-proxy-service-8981api-gateway-9990Actually JMX is enabled by default for
api-gateway, so there is no need to do anything else. To attach JVisualVM to it, the jboss-client.jar should be added in the classpath andservice:jmx:http-remoting-jmx://should be used to provide the server address.