I have tried every recipe in the book, but things just wont work today...
I am trying to use VisualVM to profile my Java app running in a remote server, so I googled and googled and googled for ways to do this and I end up with this solution:
java -Dcom.sun.management.jmxremote \
-Dcom.sun.management.jmxremote.port=9199 \
-Dcom.sun.management.jmxremote.local.only=false \
-Dcom.sun.management.jmxremote.authenticate=false \
-Dcom.sun.management.jmxremote.ssl=false \
-jar bin/felix.jar
Running this will get me JMX to run I guess, so I can see him running on 9199:
java 21947 root 9u IPv6 1811434 0t0 TCP *:7192 (LISTEN)
java 26376 root 14u IPv6 1844518 0t0 TCP *:9199 (LISTEN)
Moreover, I can test that the port is visible on the web:
Now, when I try to open the connection in VisualVM in my machine (which can also ping the jmx server) this happens:
I must be so dumb, that everyone in this world was able to put this thing running but me. Damn...
EDIT: I installed wireshark to know what's going on under the hood, so I saw this. As soon as I add a remote IP in VisualVM wireshark starts detecting this repetitive activity:
However, if I try to add a new JMX connection and ask him to connect, wireshark will not grab even one single packet of that connection attempt.
This seems to me that VisualVM is not even trying to connect, despite giving the error message "Cannot connect"...!! What the hell is going on?
Start your service using these options:
-Djava.rmi.server.hostname=193.163.XXX.XXX
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=9199
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
Then you can use jvisualvm or jconsole with just the "193.163.XXX.XXX:9199" address.