[jbosstools-issues] [JBoss JIRA] (JBIDE-23130) JMX connection to remote server does not work (fs operations, runtime)

[Martin Malina (JIRA)]

Martin Malina created JBIDE-23130:
-------------------------------------

             Summary: JMX connection to remote server does not work (fs operations, runtime)
                 Key: JBIDE-23130
                 URL: https://issues.jboss.org/browse/JBIDE-23130
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: jmx
    Affects Versions: 4.4.1.Final
            Reporter: Martin Malina


This is basically a follow up of JBIDE-22741.

It turns out even if I have a local runtime, jmx connection to a remote fs server still doesn't work for me.

1. Set up a remote WildFly 8.2 server over ssh (use fs operations, local runtime)
2. Make sure the user is set up correctly both on the server and in server editor in Eclipse
3. Start the remote server
4. Try to connect to the server in JMX Navigator
You'll get this in the error log view:
{code}
Error connecting to jmx for server WildFly  8.2 marvin
org.jboss.tools.jmx.core.JMXException: There was an error connecting to WildFly  8.2 marvin via JMX.  Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com launch arguments
	at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:98)
	at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:211)
	at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162)
	at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:341)
	at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76)
	at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
	at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.net.ConnectException: Connection refused
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
	at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:319)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:539)
	at ...asynchronous invocation...(Unknown Source)
	at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272)
	at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253)
	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351)
	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:335)
	at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:232)
	at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151)
	at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102)
	at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
	at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84)
	... 7 more
{code}
{code}
There was an error connecting to WildFly  8.2 marvin via JMX.  Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com launch arguments
java.net.ConnectException: Connection refused
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
	at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:319)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:539)
	at ...asynchronous invocation...(Unknown Source)
	at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272)
	at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253)
	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351)
	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:335)
	at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:232)
	at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151)
	at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102)
	at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
	at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84)
	at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:211)
	at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162)
	at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:341)
	at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76)
	at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
	at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}

So it tells me that I need to expose the managerment port. But we never did that for fs operations, no? And indeed it's not exposed:
{code}
 2810 pts/1    Sl     0:06              \_ java -Dprogram.name=JBossTools: WildFly  8.2 marvin -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/log/boot.log -Dlogging.configuration=file:/home/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/configuration/logging.properties -Djboss.home.dir=/home/rasp/jbossqa/runtimes/wildfly-8.2.0.Final -Dorg.jboss.logmanager.nocolor=true -jar /home/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/jboss-modules.jar -mp /home/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/modules -jaxpmodule javax.xml.jaxp-provider -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/home/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone
{code}

But even if I do expose the management port, it still won't work - then I hit JBIDE-20108 .

Anyway, I think we didn't need to expose the management port in the past. Or did we?



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)