Has anyone ever got a remote JMX JConsole to work

Question

It seems that I ve never got this to work in the past  Currently  I KNOW it doesn t work   But we start up our Java process   -Dcom sun management jmxremote -Dcom sun management jmxremote port 6002 -Dcom sun management jmxremote authenticate false -Dcom sun management jmxremote ssl false   I can telnet to the port  and  something is there   that is  if I don t start the process  nothing answers  but if I do  it does   but I can not get JConsole to work filling in the IP and port   Seems like it should be so simple  but no errors  no noise  no nothing  Just doesn t work   Anyone know the hot tip for this

User · Answer

I have a solution for this   If your Java process is running on Linux behind a firewall and you want to start JConsole   Java VisualVM   Java Mission Control on Windows on your local machine to connect it to the JMX Port of your Java process   You need access to your linux machine via SSH login  All Communication will be tunneled over the SSH connection   TIP  This Solution works no matter if there is a firewall or not   Disadvantage  Everytime you restart your java process  you will need to do all steps from 4 - 9 again       1  You need the putty-suite for your Windows machine from here      http   www chiark greenend org uk  sgtatham putty download html      At least the putty exe       2  Define one free Port on your linux machine    lt jmx-remote-port gt    Example   jmx-remote-port   15666             3  Add arguments to java process on the linux machine  This must be done exactly like this  If its done like below  it works for linux Machines behind firewalls  It works cause of the -Djava rmi server hostname localhost argument    -Dcom sun management jmxremote -Dcom sun management jmxremote port  lt jmx-remote-port gt  -Dcom sun management jmxremote ssl false -Dcom sun management jmxremote authenticate false -Dcom sun management jmxremote local only false -Djava rmi server hostname localhost   Example   java -Dcom sun management jmxremote -Dcom sun management jmxremote port 15666 -Dcom sun management jmxremote ssl false -Dcom sun management jmxremote authenticate false -Dcom sun management jmxremote local only false -Djava rmi server hostname localhost ch sushicutta jmxremote Main       4  Get Process-Id of your Java Process  ps -ef   grep  lt java-processname gt   result --- gt   lt process-id gt    Example   ps -ef   grep ch sushicutta jmxremote Main  result --- gt  24321       5  Find arbitrary Port for RMIServer stubs download  The java process opens a new TCP Port on the linux machine  where the RMI Server-Stubs will be available for download  This port also needs to be available via SSH Tunnel to get a connection to the Java Virtual Machine   With netstat -lp this port can be found also the lsof -i gives hints what port has been opened form the java process   NOTE  This port always changes when java process is started   netstat -lp   grep  lt process-id gt   tcp        0      0    lt jmx-remote-port gt              LISTEN      24321 java tcp        0      0    lt rmi-server-port gt              LISTEN      24321 java   result --- gt   lt rmi-server-port gt    Example   netstat -lp   grep 24321  tcp        0      0   15666             LISTEN      24321 java tcp        0      0   37123             LISTEN      24321 java   result --- gt  37123     6  Enable two SSH-Tunnels from your Windows machine with putty  Source port   lt jmx-remote-port gt  Destination  localhost  lt jmx-remote-port gt   x  Local         x  Auto         Source port   lt rmi-server-port gt  Destination  localhost  lt rmi-server-port gt   x  Local         x  Auto   Example   Source port  15666 Destination  localhost 15666  x  Local         x  Auto         Source port  37123 Destination  localhost 37123  x  Local         x  Auto             7  Login to your Linux machine with Putty with this SSH-Tunnel enabled   Leave the putty session open    When you are logged in  Putty will tunnel all TCP-Connections to the linux machine over the SSH port 22   JMX-Port   Windows machine  localhost 15666    gt  gt  gt  SSH  gt  gt  gt    linux machine  localhost 15666   RMIServer-Stub-Port   Windows Machine  localhost 37123    gt  gt  gt  SSH  gt  gt  gt    linux machine  localhost 37123       8  Start JConsole   Java VisualVM   Java Mission Control to connect to your Java Process using the following URL  This works  cause JConsole   Java VisualVM   Java Mission Control thinks you connect to a Port on your local Windows machine  but Putty send all payload to the port 15666 to your linux machine   On the linux machine first the java process gives answer and send back the RMIServer Port  In this example 37123   Then JConsole   Java VisualVM   Java Mission Control thinks it connects to localhost 37123 and putty will send the whole payload forward to the linux machine  The java Process answers and the connection is open    x  Remote Process  service jmx rmi    jndi rmi   localhost  lt jndi-remote-port gt  jmxrmi   Example    x  Remote Process  service jmx rmi    jndi rmi   localhost 15666 jmxrmi              9  ENJOY  8-

User · Answer

I am running JConsole JVisualVm on windows hooking to tomcat running Linux Redhat ES3   Disabling packet filtering using the following command did the trick for me    usr sbin iptables -I INPUT -s jconsole-host -p tcp --destination-port jmxremote-port -j ACCEPT   where jconsole-host is either the hostname or the host address on which JConsole runs on and jmxremote-port is the port number set for com sun management jmxremote port for remote management

User · Answer

When testing debugging diagnosing remote JMX problems  first always try to connect on the same host that contains the MBeanServer  i e  localhost   to rule out network and other non-JMX specific problems

User · Answer

Tried with Java 8 and newer versions  This solution works well also with firewalls  1  Add this to your java startup script on remote-host   -Dcom sun management jmxremote port 1616 -Dcom sun management jmxremote rmi port 1616 -Dcom sun management jmxremote ssl false -Dcom sun management jmxremote authenticate false -Dcom sun management jmxremote local only false -Djava rmi server hostname localhost   2  Execute this on your computer    Windows users   putty exe -ssh user remote-host -L 1616 remote-host 1616 Linux and Mac Users   ssh user remote-host -L 1616 remote-host 1616   3  Start jconsole on your computer  jconsole localhost 1616   4  Have fun   P S   during step 2  using ssh and -L you specify that the port 1616 on the local  client  host must be forwarded to the remote side  This is an ssh tunnel and helps to avoids firewalls or various networks problems

User · Answer

In order to make a contribution  this is what I did on CentOS 6 4 for Tomcat 6    Shutdown iptables service  service iptables stop  Add the following line to tomcat6 conf  CATALINA OPTS    CATALINA OPTS  -Dcom sun management jmxremote -Dcom sun management jmxremote port 8085 -Dcom sun management jmxremote ssl false -Dcom sun management jmxremote authenticate false -Djava rmi server hostname  host ip      This way I was able to connect from another PC using JConsole

User · Answer

Adding -Djava rmi server hostname   lt host ip gt   resolved this problem for me

User · Answer

I m using boot2docker to run docker containers with Tomcat inside and I ve got the same problem  the solution was to    Add -Djava rmi server hostname 192 168 59 103 Use the same JMX port in host and docker container  for instance  docker run     -p 9999 9999      Using different ports does not work

User · Answer

These are the steps that worked for me  debian behind firewall on the server side  reached over VPN from my local Mac    check server ip  hostname -i   use JVM params   -Dcom sun management jmxremote -Dcom sun management jmxremote port  jmx port  -Dcom sun management jmxremote local only false -Dcom sun management jmxremote authenticate false -Dcom sun management jmxremote ssl false -Djava rmi server hostname  server ip from step 1    run application  find pid of the running java process  check all ports used by JMX RMI  netstat -lp   grep  pid from step 4    open all ports from step 5 on the firewall  Voila

User · Answer

You need to also make sure that your machine name resolves to the IP that JMX is binding to  NOT localhost nor 127 0 0 1   For me  it has helped to put an entry into hosts that explicitly defines this

User · Answer

Check if your server is behind the firewall  JMX is base on RMI  which open two port when it start  One is the register port  default is 1099  and can be specified by the com sun management jmxremote port option  The other is for data communication  and is random  which is what cause problem  A good news is that  from JDK6  this random port can be specified by the com sun management jmxremote rmi port option    export CATALINA OPTS  -Dcom sun management jmxremote -Dcom sun management jmxremote port 8991 -Dcom sun management jmxremote rmi port 8991 -Dcom sun management jmxremote authenticate false -Dcom sun management jmxremote ssl false

User · Answer

You are probably experiencing an issue with a firewall  The  problem  is that the port you specify is not the only port used  it uses 1 or maybe even 2 more ports for RMI  and those are probably blocked by a firewall   One of the extra ports will not be know up front if you use the default RMI configuration  so you have to open up a big range of ports - which might not amuse the server administrator   There is a solution that does not require opening up a lot of ports however  I ve gotten it to work using the combined source snippets and tips from  http   forums sun com thread jspa threadID 5267091 - link doesn t work anymore  http   blogs oracle com jmxetc entry connecting through firewall using jmx  http   java sun com javase 6 docs technotes guides management agent html  It s even possible to setup an ssh tunnel and still get it to work  -

User · Answer

You are probably experiencing an issue with a firewall  The  problem  is that the port you specify is not the only port used  it uses 1 or maybe even 2 more ports for RMI  and those are probably blocked by a firewall   One of the extra ports will not be know up front if you use the default RMI configuration  so you have to open up a big range of ports - which might not amuse the server administrator   There is a solution that does not require opening up a lot of ports however  I ve gotten it to work using the combined source snippets and tips from  http   forums sun com thread jspa threadID 5267091 - link doesn t work anymore  http   blogs oracle com jmxetc entry connecting through firewall using jmx  http   java sun com javase 6 docs technotes guides management agent html  It s even possible to setup an ssh tunnel and still get it to work  -

User · Answer

PROTIP    The RMI port are opened at arbitrary portnr s  If you have a firewall and don t want to open ports 1024-65535  or use vpn  then you need to do the following   You need to fix  as in having a known number  the RMI Registry and JMX RMI Server ports  You do this by putting a jar-file  catalina-jmx-remote jar it s in the extra s  in the lib-dir and configuring a special listener under server    lt Listener className  org apache catalina mbeans JmxRemoteLifecycleListener        rmiRegistryPortPlatform  10001  rmiServerPortPlatform  10002    gt     And ofcourse the usual flags for activating JMX      -Dcom sun management jmxremote        -Dcom sun management jmxremote ssl false       -Dcom sun management jmxremote authenticate false       -Djava rmi server hostname  lt HOSTNAME gt      See  JMX Remote Lifecycle Listener at http   tomcat apache org tomcat-6 0-doc config listeners html  Then you can connect using this horrific URL    service jmx rmi    lt hostname gt  10002 jndi rmi    lt hostname gt  10001 jmxrmi

User · Answer

After putting my Google-fu to the test for the last couple of days  I was finally able to get this to work after compiling answers from Stack Overflow and this page http   help boomi com atomsphere GUID-F787998C-53C8-4662-AA06-8B1D32F9D55B html   Reposting from the Dell Boomi page   To Enable Remote JMX on an Atom  If you want to monitor the status of an Atom  you need to turn on Remote JMX  Java Management Extensions  for the Atom   Use a text editor to open the  lt atom installation directory gt  bin atom vmoptions file   Add the following lines to the file   -Dcom sun management jmxremote port 5002 -Dcom sun management jmxremote rmi port 5002 -Dcom sun management jmxremote authenticate false -Dcom sun management jmxremote ssl false   The one line that I haven t seen any Stack Overflow answer cover is   -Dcom sun management jmxremote rmi port 5002   In my case  I was attempting to retrieve Kakfa metrics  so I simply changed the above option to match the -Dcom sun management jmxremote port value  So  without authentication of any kind  the bare minimum config should look like this   -Dcom sun management jmxremote -Dcom sun management jmxremote authenticate false -Dcom sun management jmxremote ssl false -Dcom sun management jmxremote port  jmx remote port   -Dcom sun management jmxremote local only false -Dcom sun management jmxremote rmi port  jmx remote port  -Djava rmi server hostname  CNAME IP Address

User · Answer

The following worked for me  though I think port 2101 did not really contribute to this    -Dcom sun management jmxremote port 2100 -Dcom sun management jmxremote authenticate false -Dcom sun management jmxremote ssl false -Dcom sun management jmxremote local only false -Dcom sun management jmxremote rmi port 2101 -Djava rmi server hostname  lt IP ADDRESS gt OR lt HOSTNAME gt    I am connecting from a remote machine to a server which has Docker running and the process is inside the container  Also  I stopped firewallD but I don t think that was the issue as I could telnet to 2100 even with the firewall open  Hope it helps

User · Answer

When testing debugging diagnosing remote JMX problems  first always try to connect on the same host that contains the MBeanServer  i e  localhost   to rule out network and other non-JMX specific problems

User · Answer

Getting JMX through the Firewall is really hard  The Problem is that standard RMI uses a second random assigned port  beside the RMI registry    We have three solution that work  but every case needs a different one    JMX over SSH Tunnel with Socks proxy  uses standard RMI with SSH magic http   simplygenius com 2010 08 jconsole-via-socks-ssh-tunnel html JMX MP  alternative to standard RMI   uses only one fixed port  but needs a special jar on server and client http   meteatamel wordpress com 2012 02 13 jmx-rmi-vs-jmxmp  Start JMX Server form code  there it is possible to use standard RMI and use a fixed second port  https   issues apache org bugzilla show bug cgi id 39055

User · Answer

Are you running on Linux  Perhaps the management agent is binding to localhost   http   java sun com j2se 1 5 0 docs guide management faq html linux1

User · Answer

Sushicutta s steps 4-7 can be skipped by adding the following line to step 3   -Dcom sun management jmxremote rmi port  lt same port as jmx-remote-port gt    e g  Add to start up parameters   -Dcom sun management jmxremote -Dcom sun management jmxremote port 12345 -Dcom sun management jmxremote rmi port 12345 -Dcom sun management jmxremote ssl false -Dcom sun management jmxremote authenticate false -Dcom sun management jmxremote local only false -Djava rmi server hostname localhost   For the port forwarding  connect using   ssh -L 12345 localhost 12345  lt username gt   lt host gt    if your host is a stepping stone  simply chain the port forward by running the following on the step stone after the above   ssh -L 12345 localhost 12345  lt username gt   lt host2 gt    Mind that the hostname localhost is needed to make sure the jmxremote is telling the rmi connection to use the tunnel  Otherwise it might try to connect directy and hit the firewall

User · Answer

I m trying to JMC to run the Flight Recorder  JFR  to profile NiFi on a remote server that doesn t offer a graphical environment on which to run JMC   Based on the other answers given here  and upon much trial and error  here is what I m supplying to the JVM  conf bootstrap conf when I launch NiFi   java arg 90 -Dcom sun management jmxremote true java arg 91 -Dcom sun management jmxremote port 9098 java arg 92 -Dcom sun management jmxremote rmi port 9098 java arg 93 -Dcom sun management jmxremote authenticate false java arg 94 -Dcom sun management jmxremote ssl false java arg 95 -Dcom sun management jmxremote local only false java arg 96 -Djava rmi server hostname 10 10 10 92   the IP address of my server running NiFi    I did put this in  etc hosts  though I doubt it s needed   10 10 10 92   localhost   Then  upon launching JMC  I create a remote connection with these properties   Host  10 10 10 92 Port  9098 User   nothing  Password   ibid    Incidentally  if I click the Custom JMX service URL  I see   service jmx rmi    jndi rmi   10 10 10 92 9098 jmxrmi   This finally did it for me

User · Answer

Getting JMX through the firewall isn t that hard at all  There is one small catch  You have to forward both your JMX configured port ie  9010 and one of dynamic ports its listens to on my machine it was   30000

User · Answer

There are already some great answers here  but  there is a slightly simpler approach that I think it is worth sharing   sushicutta s approach is good  but is very manual as you have to get the RMI Port every time  Thankfully  we can work around that by using a SOCKS proxy rather than explicitly opening the port tunnels  The downside of this approach is JMX app you run on your machine needs to be able to be configured to use a Proxy  Most processes you can do this from adding java properties  but  some apps don t support this   Steps    Add the JMX options to the startup script for your remote Java service   -Dcom sun management jmxremote true -Dcom sun management jmxremote port 8090 -Dcom sun management jmxremote ssl false -Dcom sun management jmxremote authenticate false  Set up a SOCKS proxy connection to your remote machine   ssh -D 9696 user remotemachine com  Configure your local Java monitoring app to use the SOCKS proxy  localhost 9696    Note  You can sometimes do this from the command line  i e    jconsole -J-DsocksProxyHost localhost -J-DsocksProxyPort 9696

[jmx] Has anyone ever got a remote JMX JConsole to work?

1. You need the putty-suite for your Windows machine from here:

2. Define one free Port on your linux machine:

Example:

3. Add arguments to java process on the linux machine

Example:

4. Get Process-Id of your Java Process

Example:

5. Find arbitrary Port for RMIServer stubs download

Example:

6. Enable two SSH-Tunnels from your Windows machine with putty

Example:

7. Login to your Linux machine with Putty with this SSH-Tunnel enabled.

8. Start JConsole / Java VisualVM / Java Mission Control to connect to your Java Process using the following URL

Example:

9. ENJOY #8-]

Examples related to jmx

Examples related to jconsole