[jbosstools-issues] [JBoss JIRA] (JBIDE-22761) Connection to local EAP 7 via jmx fails
Radim Hopp (JIRA)
issues at jboss.org
Tue Jul 19 10:19:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-22761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267521#comment-13267521 ]
Radim Hopp commented on JBIDE-22761:
------------------------------------
{noformat:title=Error connecting to jmx for server jboss-eap-7.0}
org.jboss.tools.jmx.core.JMXException: There was an error connecting to jboss-eap-7.0 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:202)
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:332)
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.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:288)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:269)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:367)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351)
at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:239)
at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:158)
at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:105)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84)
... 6 more{noformat}
Clean workspace don't help.
Fedora 24
OpenJDK 1.8.0_92
Devstudio 10.0.1.AM2-v20160715-2233-B5663
> Connection to local EAP 7 via jmx fails
> ---------------------------------------
>
> Key: JBIDE-22761
> URL: https://issues.jboss.org/browse/JBIDE-22761
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.4.1.AM2
> Reporter: Martin Malina
>
> This was spotted by Radim on linux today - he added EAP 7 via runtime detection, then started it and then tried to connect via jmx and it failed for him.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list