blocks|key|1265632|text|你说“但是连接不成功”到底是什么意思？是否有错误消息？尝试打开jconsole中的日志，看看这是否有助于调试它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1265633|要打开jconsole日志记录，在将要运行jconsole的目录中编辑一个名为logging.properties的文件，添加：|1265634|handlers=+java.util.logging.ConsoleHandler

.level=INFO

java.util.logging.FileHandler.pattern+=+%25h/java%25u.log
java.util.logging.FileHandler.limit+=+50000
java.util.logging.FileHandler.count+=+1
java.util.logging.FileHandler.formatter+=+java.util.logging.XMLFormatter

java.util.logging.ConsoleHandler.level+=+FINEST
java.util.logging.ConsoleHandler.formatter+=+java.util.logging.SimpleFormatter

javax.management.level=FINEST
javax.management.remote.level=FINEST|code-block|syntax|javascript|1265635|然后，使用以下命令启动jconsole：|1265636|jconsole+-J-Djava.util.logging.config.file=logging.properties|1265637|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

What exactly do you mean when you say "But can't connect successfully."? Is there an error message? Try turning on logging in jconsole and see if that helps debug it.

To turn on jconsole logging, edit a file named logging.properties in the directory you will be running jconsole in, add:

<pre><code>handlers= java.util.logging.ConsoleHandler

.level=INFO

java.util.logging.FileHandler.pattern = %h/java%u.log
java.util.logging.FileHandler.limit = 50000
java.util.logging.FileHandler.count = 1
java.util.logging.FileHandler.formatter = java.util.logging.XMLFormatter

java.util.logging.ConsoleHandler.level = FINEST
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter

javax.management.level=FINEST
javax.management.remote.level=FINEST
</code></pre>

Then, start jconsole with:

<pre><code>jconsole -J-Djava.util.logging.config.file=logging.properties
</code></pre>

blocks|key|1265682|text|我遇到了类似的问题，如果不是相同的话。如果在机器上本地启动jconsole，我就可以连接到JMX服务器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1265683|RMI服务器似乎没有在正确的ip上侦听。因此，按照this+related+question中的建议，我添加了以下内容：|offset|length|1265684|-Djava.rmi.server.hostname=<host+ip>|code-block|syntax|javascript|1265685|对JAVA_OPTS也是如此，然后它就起作用了。|style|CODE|1265686|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/151238/has-anyone-ever-got-a-remote-jmx-jconsole-to-work^0|0|P|L|0|0|0|1|9|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|12|8|@$D|13|E|14|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

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 <a href="https://stackoverflow.com/questions/151238/has-anyone-ever-got-a-remote-jmx-jconsole-to-work">this related question</a>, I added the following:

<pre><code>-Djava.rmi.server.hostname=&lt;host ip&gt;
</code></pre>

to <code>JAVA_OPTS</code> as well, and then it worked.

blocks|key|1480352|text|您使用哪个字符串作为JMX连接url。我不想指出显而易见的事实，但JConsole的界面很糟糕，在我看来，它需要一个过于复杂的url才能连接到远程jmx应用程序。我的是这样的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1480353|service:jmx:rmi:///jndi/rmi://(hostname):(jmxport)/jmxrmi|code-block|syntax|javascript|1480354|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

what string are you using as the JMX connection url. I don't mean to point out the obvious but JConsole has a terrible interface and to me requires an overly complex url before it will connect to a remote jmx app. Mine looks like this:

<pre><code>service:jmx:rmi:///jndi/rmi://(hostname):(jmxport)/jmxrmi
</code></pre>

blocks|key|1265786|text|更改linux上的/etc/hosts，将与我的帐户相关联的本地主机地址替换为机器ip，为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1265787|entityMap^0|9|A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Changing the <code>/etc/hosts</code> on linux, where I replaced the localhost address associated to my account to the machine ip, solved this problem for me.

blocks|key|1480489|text|我收集了网上散布的信息，这些信息是通过其他成员的提示找到的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1480490|JMX造成的最大痛苦是(imo)，JMX打开了第二个动态分配的网络端口。防火墙(如iptables)将阻止此操作。|1480491|linux上tomcat的解决方案：|1480492|使用tomcat6.0.24或更新版本从apache+tomcat附加软件下载catalina-jmx-remote.jar+(使用tomcat下载页面上的浏览)，将其复制到$CTALINA_HOME\lib中|1480493|这允许您设置JMX使用的两个端口|1480494|编辑server.xml中的服务器部分|1480495|<Server+port="8005"+..>
++...
++<Listener+className="org.apache.catalina.mbeans.JmxRemoteLifecycleListener"+rmiRegistryPortPlatform="9840"+rmiServerPortPlatform="9841"/>|code-block|syntax|javascript|1480496|设置一些环境变量(例如在setenv.sh中)|1480497|CATALINA_OPTS="
++-Djava.rmi.server.hostname=IP-TO-LISTEN
++-Dcom.sun.management.jmxremote.password.file=$CATALINA_BASE/conf/jmxremote.password+
++-Dcom.sun.management.jmxremote.access.file=$CATALINA_BASE/conf/jmxremote.access+
++-Dcom.sun.management.jmxremote.ssl=false"|1480498|这将激活JMX的访问控制|1480499|jmxremote.access将如下所示|1480500|monitorRole+readonly
controlRole+readwrite|1480501|end+jmxremote.password将为|1480502|monitorRole+tomcat
controlRole+tomcat|1480503|(只是简单的空格)|1480504|重新启动tomcat。|1480505|现在在服务器上配置防火墙(例如iptables)|1480506|/etc/sysconfig/iptables|1480507|-A+RH-Firewall-1-INPUT+-m+state+--state+NEW+-m+tcp+-p+tcp+--dport+9840+-j+ACCEPT
-A+RH-Firewall-1-INPUT+-m+state+--state+NEW+-m+tcp+-p+tcp+--dport+9841+-j+ACCEPT|1480508|和/etc/sysconfig/ip6tables|1480509|-A+RH-Firewall-1-INPUT+-m+tcp+-p+tcp+--dport+9840+-j+ACCEPT
-A+RH-Firewall-1-INPUT+-m+tcp+-p+tcp+--dport+9841+-j+ACCEPT|1480510|重新启动iptables|1480511|完成了！|1480512|现在在您的工作站上使用VisualVM或JConsole建立到我们示例中的rmiRegistryPortPlatform+9840的连接。|1480513|如果工作站和服务器之间没有更多的防火墙，它应该可以工作。|1480514|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1U|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1V|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1W|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1X|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1Y|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|S|3|T|5|N|7|20|8|@]|9|@]|A|$O|P]]|$1|U|3|V|5|6|7|21|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|22|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|N|7|23|8|@]|9|@]|A|$O|P]]|$1|10|3|11|5|6|7|24|8|@]|9|@]|A|$]]|$1|12|3|13|5|N|7|25|8|@]|9|@]|A|$O|P]]|$1|14|3|15|5|6|7|26|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|27|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|28|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|29|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|N|7|2A|8|@]|9|@]|A|$O|P]]|$1|1E|3|1F|5|6|7|2B|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|N|7|2C|8|@]|9|@]|A|$O|P]]|$1|1I|3|1J|5|6|7|2D|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|2E|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|2F|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|2G|8|@]|9|@]|A|$]]|$1|1Q|3|-4|5|6|7|2H|8|@]|9|@]|A|$]]]|1R|$]]

I've collected information spread over the net, found with hints from other members.

Most pain caused by JMX is (imo) the fact that JMX opens a second dynamically allocated network port. A firewall (like iptables) will block this.

Solution for tomcat on linux :

use tomcat 6.0.24 or newer
download catalina-jmx-remote.jar from apache tomcat extras (use browse on tomcat download page)
copy it in the $CTALINA_HOME\lib

This allows you to set both ports used by JMX

edit Server section in your server.xml

<pre><code>&lt;Server port="8005" ..&gt;
 ...
 &lt;Listener className="org.apache.catalina.mbeans.JmxRemoteLifecycleListener" rmiRegistryPortPlatform="9840" rmiServerPortPlatform="9841"/&gt;
</code></pre>

set some environment variables (e.g. in setenv.sh) 

<pre><code>CATALINA_OPTS="
 -Djava.rmi.server.hostname=IP-TO-LISTEN
 -Dcom.sun.management.jmxremote.password.file=$CATALINA_BASE/conf/jmxremote.password 
 -Dcom.sun.management.jmxremote.access.file=$CATALINA_BASE/conf/jmxremote.access 
 -Dcom.sun.management.jmxremote.ssl=false"
</code></pre>

this activates access control for JMX

jmxremote.access will look like

<pre><code>monitorRole readonly
controlRole readwrite
</code></pre>

end jmxremote.password will be 

<pre><code>monitorRole tomcat
controlRole tomcat
</code></pre>

(just simple spaces)

restart tomcat.

Now configure firewall on the server (e.g. iptables)

/etc/sysconfig/iptables

<pre><code>-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 9840 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 9841 -j ACCEPT
</code></pre>

and /etc/sysconfig/ip6tables

<pre><code>-A RH-Firewall-1-INPUT -m tcp -p tcp --dport 9840 -j ACCEPT
-A RH-Firewall-1-INPUT -m tcp -p tcp --dport 9841 -j ACCEPT
</code></pre>

restart iptables 

Done!

Now use VisualVM or JConsole on your workstation to establish a connection to rmiRegistryPortPlatform, 9840 in our sample.

If there are no more firewalls between workstation and server it should work.

blocks|key|1480558|text|嗯，我在Linux机器(虚拟机)中遇到了这个问题，我用-Djava.rmi.server.hostname属性解决了这个问题，但是有一件事我不能理解。我的机器有5个tomcat服务器，它们都在连续的端口(8008,8018,8028...)中启用了jmx。其中只有一个连接JMX的问题。没有防火墙，在任何tomcat中都没有-Djava.rmi.server.hostname属性....|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1480559|所以问题是我理解这个问题，但我不能理解为什么我的tomcats中有4个可以工作，而其中1个不能。|1480560|P.D:我知道我的英语很差。我很抱歉。|1480561|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Well, I had this problem in a Linux box (virtual machine) and I fixed it using -Djava.rmi.server.hostname property but there's a thing I can't understand. My machine has 5 tomcat servers, all of them has jmx enabled in consecutive ports (8008,8018,8028...) and only one of them had this issue connecting JMX. No firewall, no -Djava.rmi.server.hostname property in any tomcat....

So the thing is that I understand the problem but I can't understand why 4 of my tomcats worked and 1 of them not.

P.D: My english is very poor, I know. My Apologies.

blocks|key|1265966|text|PROTIP:您需要修复RMI注册表和JMX/RMI服务器端口。您可以通过将jar-file放入lib-dir并配置一个特殊的侦听器来实现这一点。(当然还有激活JMX的常用标志|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1265967|++++-Dcom.sun.management.jmxremote++\
++++-Dcom.sun.management.jmxremote.port=8999+\
++++-Dcom.sun.management.jmxremote.ssl=false+\
++++-Dcom.sun.management.jmxremote.authenticate=false+\
++++-Djava.rmi.server.hostname=<HOSTNAME>+\|code-block|syntax|javascript|1265968|请参阅http://tomcat.apache.org/tomcat-6.0-doc/config/listeners.html上的JMX+Remote+Lifecycle+Listener|offset|length|1265969|entityMap|0|LINK|mutability|MUTABLE|url|http://tomcat.apache.org/tomcat-6.0-doc/config/listeners.html^0|0|0|3|1P|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

PROTIP: You need to fix (as in having a known number) the RMI Registry and JMX/RMI Server ports. You do this by putting jar-file in the lib-dir and configuring a special listener. (And ofcourse the usual flags for activating JMX

<pre><code> -Dcom.sun.management.jmxremote \
 -Dcom.sun.management.jmxremote.port=8999 \
 -Dcom.sun.management.jmxremote.ssl=false \
 -Dcom.sun.management.jmxremote.authenticate=false \
 -Djava.rmi.server.hostname=&lt;HOSTNAME&gt; \
</code></pre>

See: JMX Remote Lifecycle Listener at <a href="http://tomcat.apache.org/tomcat-6.0-doc/config/listeners.html" rel="nofollow">http://tomcat.apache.org/tomcat-6.0-doc/config/listeners.html</a>

blocks|key|1266010|text|如果您在linux上工作，请修改catalina.sh文件，添加以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1266011|++++++++++++++++CATALINA_OPTS="-Dcom.sun.management.jmxremote+-Djava.rmi.server.hostname=<HOST_IP>+-Dcom.sun.management.jmxremote.port=<HOST_PORT>+-Dcom.sun.management.jmxremote.ssl=false+-Dcom.sun.management.jmxremote.authenticate=false"
++++++++++++export+CATALINA_OPTS|code-block|syntax|javascript|1266012|或者以root用户身份修改/etc/profile文件，然后重新运行该文件(源/etc/profile)|1266013|如果您在windows上工作，并且从命令行启动tomcat，请使用环境变量CATALINA_OPTS|1266014|如果您正在windows上工作，并且将tomcat作为服务启动，则需要使用监视器服务实用程序来配置服务初始化参数(+setenv.bat、catalina.bat或env-vars都不起作用)。为此，您需要在services.msc中列出的服务名称(例如jasperreportsTomcat)。之后，您需要以管理员身份打开控制台并执行(例如)：tomcat6w.exe+//MS//jasperreportsTomcat|1266015|使用此命令将出现一个托盘图标，您可以在其中打开一个面板。在"Java“选项卡中，您现在可以修改jmx选项。注意不要添加尾随的空格，并使用"enter“符号逐行分隔每个选项。|1266016|-Dcom.sun.management.jmxremote
-Djava.rmi.server.hostname=192.168.61.101
-Dcom.sun.management.jmxremote.port=9999
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false|1266017|希望能有所帮助|1266018|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

if you are working on linux, modify the catalina.sh file adding:

<pre><code> CATALINA_OPTS="-Dcom.sun.management.jmxremote -Djava.rmi.server.hostname=&lt;HOST_IP&gt; -Dcom.sun.management.jmxremote.port=&lt;HOST_PORT&gt; -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"
 export CATALINA_OPTS
</code></pre>

or modify the /etc/profile file as root and rerun the file (source /etc/profile)

if you are working on windows and you are starting tomcat from the command line, use
 the environment variable CATALINA_OPTS

if you are working on windows and you are starting tomcat as a service, you'll need to use the monitor service utility to configure the service initialization parameters (neither setenv.bat, catalina.bat or env-vars will work). for that you'll need the service name that appears listed in services.msc (for example jasperreportsTomcat). After, you'll need to open a console as administrator and execute (for example): 
 tomcat6w.exe //MS//jasperreportsTomcat

with this command will appear a tray icon where you can open a panel. In the "Java" tab now you can modify the jmx options. Be careful to not add trailing whitespaces and use the "[enter]" symbol to separate each option line by line.

<pre><code>-Dcom.sun.management.jmxremote
-Djava.rmi.server.hostname=192.168.61.101
-Dcom.sun.management.jmxremote.port=9999
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
</code></pre>

Hope it helps

blocks|key|1480688|text|我有东西给你们所有人，以便完成这整件事的调查。有一个技巧，分析器工具使用一个端口与jvm连接，但jvm使用另一个随机端口继续对话。如果jvm在远程计算机(例如:+tomcat+web应用服务器)内运行，并且该远程计算机具有防止传出和传入连接的保护，则必须将java系统属性com.sun.management.jmxremote.rmi.port设置为与名为com.sun.management.jmxremote.port的属性相同的值|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1480689|来源：https://serverfault.com/questions/308662/how-do-i-fix-a-failed-to-retrieve-rmiserver-stub-jmx-error，也可以看看这个：http://blog.cantremember.com/debugging-with-jconsole-jmx-ssh-tunnels/|1480690|希望对大家有所贡献！|1480691|祝你好运！|1480692|entityMap|0|LINK|mutability|MUTABLE|url|https://serverfault.com/questions/308662/how-do-i-fix-a-failed-to-retrieve-rmiserver-stub-jmx-error|1|http://blog.cantremember.com/debugging-with-jconsole-jmx-ssh-tunnels/^0|3S|11|4Z|X|0|3|2R|0|33|1X|1|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@$9|11|A|12|1|13]|$9|14|A|15|1|16]]|E|$]]|$1|H|3|I|5|6|7|17|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|18|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]|T|$5|O|P|Q|E|$R|U]]]]

I got something for all of you, in order to complete the investigation of this whole thing. There is a trick, it happens that profiler tool connnects with the jvm using a port, but the jvm continues the conversation using another random port. If the jvm is running inside a remote machine (for example : a tomcat web-app server), and the remote machine has protection against outgoing and incoming connections, you must set the java system property <code>com.sun.management.jmxremote.rmi.port</code> to the same value of the property named <code>com.sun.management.jmxremote.port</code>

Source : <a href="https://serverfault.com/questions/308662/how-do-i-fix-a-failed-to-retrieve-rmiserver-stub-jmx-error">https://serverfault.com/questions/308662/how-do-i-fix-a-failed-to-retrieve-rmiserver-stub-jmx-error</a>
And also check this out : <a href="http://blog.cantremember.com/debugging-with-jconsole-jmx-ssh-tunnels/" rel="nofollow noreferrer">http://blog.cantremember.com/debugging-with-jconsole-jmx-ssh-tunnels/</a>

Hope to contribute guys!

And good luck!

blocks|key|1266143|text|检查您的服务器是否在防火墙后面。JMX基于RMI，它在启动时打开两个端口。一个是寄存器端口，缺省值为1099，可以通过com.sun.management.jmxremote.port选项指定。另一个是用于数据通信的，并且是随机的，这是导致问题的原因。好消息是，在JDK6中，这个随机端口可以由com.sun.management.jmxremote.rmi.port选项指定。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1266144|在您的{tomcat_dir}/bin/setenv.sh中添加行：|1266145|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"|code-block|syntax|javascript|1266146|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

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. 

add the line in you {tomcat_dir}/bin/setenv.sh:

<pre><code>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"
</code></pre>

I am trying to connect to a remote tomcat JMX instance using jConsole. But can't connect successfully. Any Idea?

I included the following option in remote tomcat <code>catalina.sh</code>:

<pre><code>JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote \
 -Dcom.sun.management.jmxremote.port=9004 \
 -Dcom.sun.management.jmxremote.ssl=false \
 -Dcom.sun.management.jmxremote.authenticate=false"
</code></pre>

Connecting remote tomcat JMX instance using jConsole

服务器

虚拟机

防火墙

Linux

Java

我正在尝试使用jConsole连接到远程tomcat JMX实例。但无法成功连接。有什么想法吗？我在远程tomcat catalina.sh中包含了以下选项JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote \    -Dcom.sun.management.jmx...

问使用jConsole连接远程tomcat JMX实例
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用jConsole连接远程tomcat JMX实例EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用jConsole连接远程tomcat JMX实例
EN