[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-11064: -------------------------------- Summary: JMX Connections to as7 errors out and is not usable at all. (was: RSE server startup does not work with AS 7.0.2) Fix Version/s: 3.3.0.CR1 (was: 3.3.0.Beta1) To be clear, RSE connections for startup and shutdown work just fine for as7.0.2. There are no errors in startup. The error log gets a message indicationg automatic connection to jmx has failed. Investigations will need to be done how to connect to as7 via jmx. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-11064: --------------------------------------- OK, you're right, JMX connection to AS7.1 does not work. But why isn't there an error at the startup? Do we expect it not to work and so we don't even try? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-11064: ------------------------------------- Full implementation for as71 is being committed. There was a minor api change to jmx core (ability to run a jmx command and pass in some options) put in as a new method in the interface, so any consumers of this tool on an API level must beware. There was also additions to api. Some of the utility classes that help traverse nodes would create a new connection for each and every request. If you were already within the scope of a connection, though, this was wasteful. This wasn't an issue for AS3-6, but in AS7.1 there are issues with threads staying around for a minute or more. When traversing the entire jmx tree, this leads to an out of memory exception, so new API was added with an MBeanServerConnection parameter to help maintain the scope of the operation and prevent unnecessary creation of connections. So, it's all good now! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-11064: -------------------------------- Labels: new_and_noteworthy (was: ) Component/s: jmx -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-11064: --------------------------------- Priority: Blocker (was: Major) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-11064. --------------------------------- Verified as fixed. The other issue still remains. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-11064: -------------------------------------- Ah - OK - closing again. Thx! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-11064: ------------------------------------- The only errors I am seeing for remote as7.1.0 is the following: java.lang.RuntimeException: Operation failed with status WAITING at org.jboss.remoting3.jmx.RemotingConnector.connect(RemotingConnector.java:155) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:53) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:136) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:121) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:104) at org.jboss.tools.jmx.core.tree.NodeUtils.createObjectNameTree(NodeUtils.java:51) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.loadRoot(JBossServerConnection.java:86) at org.jboss.tools.jmx.ui.internal.views.navigator.MBeanExplorerContentProvider$1.run(MBeanExplorerContentProvider.java:106) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) This also makes it not work, but I'm not seeing any NPE's anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-11064: --------------------------------------- Also, JMX connection to local AS 7.1.1 and EAP 5.1.2 work, but EAP 6.0.0 ER5 does not work currently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-11064: --------------------------------------- 6. Once I got the JMX connection for the remote 7.1.0 working, I am consistently not able to shutdown the server - the shutdown process gets started, but when it's finished, the AS is still running on the remote system. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-11064: ------------------------------------- Issue for shutdown is as follows: Once you expose the management port using -Djboss.bind.address.management=mywebsite.com, the shutdown command must change from {code}jboss-cli.sh --connect command=:shutdown{code} to {code}jboss-cli.sh --controller=website.com:9999 --connect command=:shutdown{code} Perhaps we should not be auto-exposing the management port. This seems like a bad idea and it is not secure. I will think of further ways to ensure this works without being a hindrance to the user. Pretty rough. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-11064: -------------------------------- Attachment: JBIDE-11064.v10.patch patch for b3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11064: --------------------------------------------- i've commited this path with two changes: 1) remove elements from the connector map so it does not grow forever. 2) use Map instead of HashMap. I'm not really happy with no errors shown nor logged if connections cannot be closed nor does there seem to be any handling of close being possible a long blocking method ;( -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-11064: ---------------------------------------- Attachment: jbide-11064_branch.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-11064. --------------------------------- Resolution: Done Committed to trunk, but nothing in this patch fixes or modifies the situation for RSE. RSE will not work out of the box without force-exposing their management, which is unsecure and won't be done. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-11064: ---------------------------------- Fix Version/s: 3.3.0.Beta3 (was: 3.3.0.CR1) Fix version moved to B3 since the patch was committed there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-11064. --------------------------------- OK, thanks. If we never had a working remote JMX connection to EAP 5.1.2 and nobody ever complained, I guess we don't need really need it. So I think I can finally close this JIRA now. We have other JIRAs for some remaining issues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi... ] Isaac Rooskov closed JBIDE-11064. --------------------------------- Resolution: Done -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira