[ https://issues.jboss.org/browse/JBIDE-12961?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-12961: ------------------------------------- Hi Martin: I'm investigating, but in the future, please add more details about HOW it fails. Is the problem that the mbean explorer has no ability to expand? Or does it expand but throw an error? Error where? Dialog? Error Log? etc etc. Try to include more information. Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12961?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-12961: ------------------------------------- After changing 'false' to true, the attempt to connect errors as follows {code} org.jboss.tools.jmx.core.JMXException: Error connecting to remote JMX. Please ensure your server is properly configured for JMX access. at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:147) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122) {code} If I remember correctly, it currently returns false BECAUSE we did not get it working for remote. So we simply had it do nothing instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12961?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-12961. --------------------------------- Fix Version/s: 4.0.0.Beta2 (was: 4.0.0.CR1) Resolution: Done Pushed to master. I've also updated the error log message to be more clear that ports on the remote system may be firewalled (which was an issue for me) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12961?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-12961: ----------------------------------- Assignee: Martin Malina (was: Rob Stryker) Hi Martin: It may still be a port / firewall issue. Please look at this guide to see what ports may need to be opened: https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_Applicati... On my personal setup, I've opened the following ports: 1090, 1098, 1099, 4444, 4445, 8080, 9999 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12961?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-12961: --------------------------------------- Also, I tried checking if the port is open and it seems to be ok: [rasp@marvin default]$ netstat -na | grep 1099 tcp 0 0 ::ffff:10.34.26.31:1099 :::* LISTEN [rasp@marvin default]$ netstat -na | grep 8080 tcp 0 0 ::ffff:10.34.26.31:8080 :::* LISTEN (Yes, the IPv6 address seems weird here, but web access shows the same and works fine even from a remote machine.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12961?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-12961: -------------------------------- Fix Version/s: 4.0.x (was: 4.0.0.Beta2) Tests with two local machines next to each other over IP continue to work for me. And for Xavier apparently. I did experience an issue with a remote server where eap 5.1.2 tried to repeatedly reconnect before returning from a call (and so teh call never returns), and have been unable to debug it very well. I've disabled remote firewall, and the jmx connection job continues forever. I've tracked the "forever" being due to a loop attempting to connect 10 times, with each attempt taking a very long time (stacktrace below). So the jmx connecting job seems to last forever. But so far we have two verifiers that local use on the same subnet shows the jmx connection working fine. My example of a true remote server fails, and Martin's usecase of a near-remote fails as well. I am assuming Martin's use case fails early (?) but mine takes forever. !MESSAGE Error connecting to remote JMX. Please ensure your server is properly configured for JMX access. !STACK 0 java.rmi.ConnectException: Connection refused to host: ironcloud.arcaner.com; nested exception is: java.net.ConnectException: Connection timed out at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619) at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216) at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:128) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:416) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:248) at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68) at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101) at $Proxy13.getDomains(Unknown Source) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.createConnection(JBossServerConnection.java:171) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:143) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:127) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:116) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:233) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:225) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) Caused by: java.net.ConnectException: Connection timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) at java.net.Socket.connect(Socket.java:579) at java.net.Socket.connect(Socket.java:528) at java.net.Socket.<init>(Socket.java:425) at java.net.Socket.<init>(Socket.java:208) at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40) at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:146) at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613) ... 19 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12961?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-12961: --------------------------------------- Today I tried this again. Same as usual - from Mac to RHEL6. And suddenly it works! (JBDS 6.0.0.CR1c B166, EAP 5.1.2) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira