Dropwizard JMXMP Bundle

This bundle adds support for jmx over jmxmp which is the only way to make jmx work on marathon This bundle compiles only on Java 11.

Usage

This makes it possible to use JMX over JMXMP.

Build instructions

• Clone the source:

  git clone github.com/phaneesh/dropwizard-jmxmp
  

• Build

  mvn install
  

Maven Dependency

• Use the following maven dependency:

<dependency>
    <groupId>io.dropwizard.jmxmp</groupId>
    <artifactId>dropwizard-jmxmp</artifactId>
    <version>2.0.20-1</version>
</dependency>

Using Oor bundle

Bootstrap

    @Override
    public void initialize(final Bootstrap...) {
        bootstrap.addBundle(new JmxMpBundle() {
            protected int port() {
                return 9010;
            }    
        });
    }

Note

• Make sure that the port that is being used is exposed in Dockerfile
• Make sure you define port in marathon deployment configuration
• Use these JVM arguments

 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false

• If you need remote debugging support add this JVM argument. Make sure port 5005 is exposed in Dockerfile and mapped in marathon deployment configuration

-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005

• Use the following commandline to start Jconsole with jmxmp support

jconsole -J-Djava.class.path=$JAVA_HOME/lib/tools.jar:/path/to/jmxremote_optional-repackaged-5.0.jar

• Use the following commandline to start VisualVM with jmxmp support

jvisualvm --cp:a /path/to/jmxremote_optional-repackaged-5.0.jar

• To use it with JMC add the following line in the end in jmc.ini

-Xbootclasspath/a:/path/to/jmxremote_optional-repackaged-5.0.jar

• Service URL format

service:jmx:jmxmp://<host>:<port>