Debugging JConsole Connection Failed

Question

I have a web application deployed to a remote resin server, and it has JMX turned on.

I can telnet to the remote server i.e

franz@see:/tmp$ telnet <remote-ip> 5555
Trying <remote-ip>...
Connected to <remote-ip>.
Escape character is '^]'.
��sr5javax.management.remote.message.HandshakeBeginMessage�,���6profilestLjava/lang/String;Lversionq~xppt1.0^]

telnet> q
Connection closed.

But I cannot connect to it using my JConsole

$JAVA_HOME/bin/java -cp $JAVA_HOME/lib/jconsole.jar:$JAVA_HOME/lib/tools.jar:pm-common/lib/jmxremote_optional-1_0_1_3.jar sun.tools.jconsole.JConsole service:jmx:jmxmp://<remote-ip>:5555

I have tried this with the following java versions but I get a 'Connection Failed' on both instances.

## where JAVA_HOME=/opt/java/64/jdk1.5.0_22
java version "1.5.0_22"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_22-b03, mixed mode)

## where JAVA_HOME=/opt/java/64/jdk1.6.0_17
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode)

Do you guys have any idea as to how to debug this (i.e. find out what's wrong)?

score 40 · Accepted Answer · edited Aug 06 '14 at 19:12

40

Make sure you are running your application with following java properties set

-Dcom.sun.management.jmxremote.port=9005
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false

Try to connect now. If you want to debug this ,you can run the jconsole with following command

jconsole -J-Djava.util.logging.config.file=path_to_logging.properties_for_jconsole

Below is the content of logging.properties file

Logging.properties

handlers = java.util.logging.ConsoleHandler


.level = INFO

java.util.logging.ConsoleHandler.level = FINEST

java.util.logging.ConsoleHandler.formatter = \

java.util.logging.SimpleFormatter

// Use FINER or FINEST for javax.management.remote.level - FINEST is

// very verbose...

javax.management.level = FINEST

javax.management.remote.level = FINER

Once you run jconsole a separate window will pop up displaying logs.

edited Aug 06 '14 at 19:12

eebbesen

4,946
8
48
68

answered Sep 16 '11 at 12:33

samarth

3,738
6
42
59

2

Ey! what about the missing property 'java.rmi.server.hostname'. look out for this post : http://www.gubatron.com/blog/2010/11/21/jconsole-connection-failed-retry-solved-java-jmx/ !! Hope it helps! – Victor Nov 27 '14 at 20:07
Also make sure that the password file is read protected! ie. only the user can read it - do this with chmod 600 – Mafro34 Jan 28 '15 at 07:21
Why does everyone keep going on about remote connections? I'm trying to connect locally and it still doesn't work. "Connection Failed: Retry? The connection to 15663 did not succeed." WHY? Where's the logs? Where's the error? Such a joke. – JeneralJames Dec 14 '20 at 11:46

score 25 · Answer 2 · edited Nov 28 '18 at 13:25

25

if you run jconsole -debug it gives you more diagnostic info on the failure. See the Daniel Fuchs blog entry "Troubleshooting connection problems in JConsole".

I did this and it showed me I was using 32 bit jconsole the target process was started with a different (64 bit) jvm, so apparently this isn't allowed and it was thus failing.

edited Nov 28 '18 at 13:25

answered Jan 10 '12 at 22:48

rogerdpack

56,766
33
241
361

score 10 · Answer 3 · edited Jan 20 '21 at 06:10

10

This finally made it work for me : Giving this extra option: -Djava.rmi.server.hostname=<ip addres where jvm is running

So all the vm arguments used to open jconsole from a remote machine, the jvm on the remote machine must be started with

 -Dcom.sun.management.jmxremote.authenticate=false  -Dcom.sun.management.jmxremote.port=<port> -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=<ip address>

The entire process is listed here

edited Jan 20 '21 at 06:10

Duncan Krebs

3,128
2
30
50

answered Aug 28 '14 at 08:22

Lavixu

1,328
15
20

1

This worked for me as well. Seems when you have NAT going on, you need to specify the server address. – hacket Sep 09 '14 at 17:27
After long search, adding -Djava.rmi.server.hostname= finally works for me when connecting from different machine. Below is the full arguments: java -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.local.only=false \ -Dcom.sun.management.jmxremote.port=9999 \ -Dcom.sun.management.jmxremote.authenticate=false \ -Dcom.sun.management.jmxremote.ssl=false \ -Djava.rmi.server.hostname= \ com.example.Main – Feb 05 '17 at 02:45

score 3 · Answer 4 · answered Jun 01 '11 at 11:55

3

I encountered the same Problem when starting the Java-Process through cygwin. JConsole cannot connect. Started it through win7-cmd everything works as expected.

answered Jun 01 '11 at 11:55

Stephan

31
2

Ahmet Karakaya · Answer 5 · 2013-07-18T06:24:55.493

1

I was having similar issue that remote machine was behind firewall and firewall was blocking ports defined by -Dcom.sun.management.jmxremote.port and RMI 46924. After allowing me to cnnect to these port I connected succesfully.

edited Jul 18 '13 at 06:24

answered Jul 18 '13 at 05:58

Ahmet Karakaya

9,502
21
81
133

In my case RMI port was 43702 and I found that out by debugging with logging.properties – Panu Haaramo Mar 30 '15 at 18:49

score 1 · Answer 6 · answered Mar 28 '11 at 08:12

1

I don't know if this is helpful, but perhaps you should use the the jconsole binary in the JDK bin directory rather than using the undocumented (and subject to change) sun.* classes to start up the console

answered Mar 28 '11 at 08:12

qwerty

3,635
2
25
42

Still did not work. And I don't know how to debug this either. – Franz See Apr 14 '11 at 02:59
This article (http://blogs.sun.com/jmxetc/entry/troubleshooting_connection_problems_in_jconsole) explaining common connection problems may be useful. If nothign works please review/post debug logs – qwerty Apr 14 '11 at 03:55

score 1 · Answer 7 · answered Mar 28 '11 at 08:51

1

If your application is running on JDK 1.6 then you should be able to connect it. If it is using JDK prior to 1.6 then run it with specifying the following JVM argument

-Dcom.sun.management.jmxremote

answered Mar 28 '11 at 08:51

GuruKulki

25,118
47
138
197

Does not work (tried both on JDK1.5 & JDK1.6). And I don't know how to debug it either. – Franz See Apr 14 '11 at 02:43

score 0 · Answer 8 · answered Mar 13 '19 at 18:05

If you are accessing a machine behind a firewall, you need to open both JMX and RMI ports.
In this context, you are much better off forcing the value for RMI than relying on the auto assigned
In my case, I was trying to access Tomcat so I had to do the following:

#!/bin/sh
CATALINA_OPTS="$CATALINA_OPTS -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses=true -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8008 -Dcom.sun.management.jmxremote.rmi.port=8007 -Dcom.sun.
management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"

and then

firewall-cmd --zone=public --add-port=8008/tcp --permanent
firewall-cmd --zone=public --add-port=8007/tcp --permanent
firewall-cmd --reload

Debugging JConsole Connection Failed

8 Answers8

Linked