I would prefer using JConsole for application monitoring, and it does have graphical view. If you’re using JDK 5.0 or above then it’s the best. Please refer to this using jconsole page for more details. I have been primarily using it for GC tuning and finding bottlenecks.
For completeness, the following solution worked. The JVM should be run with specific parameters established to enable remote docker JMX monitoring were as followed: -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=<PORT> -Dcom.sun.management.jmxremote.rmi.port=<PORT> -Djava.rmi.server.hostname=<IP> where: <IP> is the IP address of the host that where you executed ‘docker run’ <PORT> is the port that must be published from docker … Read more
MXBeans are just a special kind of MBeans. The main difference is that MXBean restrict the data types, so that they are “more compatible” with potential clients. As example: a MBean can expose attributes of a data type Foo. Now the client also needs to have this type Foo to make sense of the attribute. … Read more
I had a similar, if not the same, problem. I could connect to the JMX server if I started jconsole locally on the machine. It appears the RMI server was not listening on the correct ip. So, as was suggested in this related question, I added the following: -Djava.rmi.server.hostname=<host ip> to JAVA_OPTS as well, and … Read more
Now I need to connect that application from my local computer, but I don’t know the JMX port number of the remote computer. Where can I find it? Or, must I restart that application with some VM parameters to specify the port number? By default JMX does not publish on a port unless you specify … Read more
Add -Djava.rmi.server.hostname = host ip. Even i faced the same problem and this did the trick. Addition of this -Djava.rmi.server.hostname = host ip forces RMI service to use the host ip instead of 127.0.0.1
Contrary to common belief JMX/RMI doesn’t need to open all these ports. You can actually force them to be same which will mean that at the end of the day you’ll only need to punch one hole in the firewall (if firewall is your concern). Try setting System Properties: com.sun.management.jmxremote.port com.sun.management.jmxremote.rmi.port to the same value!! … Read more
There’s an even nicer way to do this using an SSH socks tunnel, since JConsole supports SOCKS: Create the SSH socks proxy locally on some free port (e.g. 7777): ssh -fN -D 7777 user@firewalled-host Run JConsole by specifying the SOCKS proxy (e.g. localhost:7777) and the address for the JMX server (e.g. localhost:2147) jconsole -J-DsocksProxyHost=localhost -J-DsocksProxyPort=7777 … Read more
I will reuse an answer I wrote up earlier for this question: Cannot connect to Tomcat’s MBeanServer via jconsole in Java6 It’s not complete, but might help: Suppose you have the JMX Server (alias ‘JMX Agent’ alias ‘the JVM you want to connect to’) running on ‘TARGET MACHINE’ with the RMI registry port at ‘RMI … Read more
At first you should run you application with these JVM params: -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9010 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false Then you should expose port for docker: EXPOSE 9010 Also specify port binding with docker run command: docker run -p 9010:9010 -it –rm –name hwd hello-world-daemon After that you can connect with Jconsole to local 9010 port and manage … Read more