[ https://jira.jboss.org/browse/JBIDE-6297?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen updated JBIDE-6297: --------------------------------------- Fix Version/s: 3.1.2 3.2.next (was: 3.1.1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6297?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on JBIDE-6297: ------------------------------------- Reading link https://community.jboss.org/wiki/WhichRemoteInterfaceShouldIUseForTheMBea..., I wonder if we could use the following: JMXServiceURL url = new JMXServiceURL(serverURL); JMXConnector jmxc = JMXConnectorFactory.connect(url, env); // Remember to call jmxc.close() when you are done with server connection. MbeanServerConnection server = jmxc.getMBeanServerConnection(); Is this what the patch is trying to do? I haven't yet looked at the source for StopLaunchConfiguration.java, but now is a good time to do that. Please supply me with a subversion url and I will check it out. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6297?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on JBIDE-6297: ------------------------------------- Usage for AS shutdown (as of M3) is described here http://pastebin.com/R8yuV7fZ Usage for AS shutdown in earlier releases is here http://pastebin.com/GHvkTvFc For the typical, localhost based shutdown, the following command should work for both old and new releases: shutdown -S If we need to shutdown a remote AS server, the following form will work with AS 6 M3 and greater: shutdown.sh --host=localhost --port=1090 -S For older AS servers, the current URL (with host/port embedded) approach would be used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6297?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen commented on JBIDE-6297: -------------------------------------------- Scott, are you suggesting we move to use only the batch scripts for both startup and shutdown ? I would actually like to do that but everytime we've tried we have bumped into the problems that we can't grab the console output of the javavm being launched by the scripts, problems with having eclipse debugger connect, the scripts have different behavior on various platforms and some set flags others don't which is why using the JMX and "raw" java vm access isolate us from all that stuff. Of course that also opens us up for disconnects between what goes on in those scripts - but shouldn't those script be really really dumb and not really have any setup to be portable ? Also it would be really great if we could avoid having to use any client jars at all since we can't easily guarantee that users have the right matching binary version that is running remote - of course we can just tell users to have that but it would be extremely useful if all of this did not requrie any binary coupling. What do you think ? What are our options ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6297?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen commented on JBIDE-6297: -------------------------------------------- yeah, but that's a very direct binary dependency ain't it ? Well, I guess its fine as long as we just launch it externally based on some *standard* set of jars which will always stay in the same place in AS 6.x releases...which jars would that be btw. ? We use jmx in a few other places too. We use it to check if the server is actually up; we use it to tell it to not scan a directoy while we are deploying and we tell it to start scanning when we are done copying (all of that we could remove if AS provided a "rest-y" API for us to use to handle full and incremental deployment) Is that url changed *only* for the shutdown ? I assume (not looked at the code yet) it also affects all the other jmx interactions ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6297?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on JBIDE-6297: ------------------------------------- True, the URL syntax is now based on JSR-160 and is also used for other remote JMX connectivity such as "twiddle" (as well as remote JMX access code). I agree about the "simplicity lost" and countered that with new (shutdown/twiddle) "--host=" + "--port=" options which are better than specifying a URL. Even simpler, just use "./shutdown.sh -S". Internally, this translates into "./shutdown.sh -s service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi -S" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6297?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on JBIDE-6297: ------------------------------------- Max, I'm not disagreeing with you. However, I'm not taking the bait to turn this jira discussion into a redesign discussion. :-) I'm all for solving the problems that you are bringing up. I'll get on #jboss-dev in a bit and maybe we can discuss further there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6297?page=com.atlassian.jira.plugin.s... ] Rob Stryker commented on JBIDE-6297: ------------------------------------ It also fails if users have two or more servers up and running, as it might misidentify which server you're shutting down. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6297?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen commented on JBIDE-6297: -------------------------------------------- Scott, sorry for missing you comment about #jboss-dev (btw. jira's is fine for design discussions IMO :). I'll try and hang out in there to catch you. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6297?page=com.atlassian.jira.plugin.s... ] Rob Stryker commented on JBIDE-6297: ------------------------------------ To be clear, I've committed this to trunk and to 3.1.2. I'm not sure on the ordering for 3.2.next so I've not committed it there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6297?page=com.atlassian.jira.plugin.s... ] Rob Stryker resolved JBIDE-6297. -------------------------------- Fix Version/s: 3.2.0.Beta2 (was: 3.2.x) Resolution: Done jira cleanup -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira