[ https://issues.jboss.org/browse/JBIDE-8301?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-8301: ------------------------------------ The behaviour currently is as follows: 1) When starting a server, a ping is launched to see if the server is up already or not. 2) If the server is up, it simply sets the tooling state to "Started". No remote command is executed 3) If the server is down, a remote launch is executed. The arguments for this remote launch can be seen in the launch configuration, which should have a remote tab for startup and shutdown commands. The behaviour when stopping is as follows: 1) A remote stop command is executed. 2) If any exception is thrown during execution (such as remote folder does not exist, shell cannot be created, etc,) the stop fails and the server state remains in state "started". 3) Otherwise, the server is put into 'stopped' mode. The semantics for stopping an already-started server can be set manually in the launch configuration, but, they default to {jboss_home}/bin/shutdown.sh -S -s hostName:port -u user -p pass in the case of most jboss installations, or, for AS-6 installations, {jboss_home}/bin/shutdown.sh -S -s service:jmx:rmi:///jndi/rmi://host:port/jmxrmi. It is assumed these are reasonable defaults, however, the user can change these all they want in the launch configuration. I would love to hear any and all suggestions you have for what behaviour should change or what is currently unacceptable. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8301?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8301: -------------------------------------------- How do I avoid any remote stop command to be executed ? i.e. just disconnect ? Same for start. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8301?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8301: -------------------------------------------- I have no idea why you think there needs to be a command executed for the state to be correct when it says "started". I prefer that I have an option to say "do not execute any start/stop commands for this server - just assume it is running and if you can let me know nicely if the server is running or not". The usecase being I simply want to deploy to an *already* running server - *no* commands should be executed at neither start or stop. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8301?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-8301: --------------------------------------- Fix Version/s: (was: 3.2.1.CR1) Labels: as_backwards (was: ) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8301?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-8301: --------------------------------------- Fix Version/s: 3.3.0.M3 (was: 3.3.0.M2) Priority: Blocker (was: Critical) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8301?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-8301: --------------------------------------- Assignee: Rob Stryker (was: Max Rydahl Andersen) Rob - for you to look at while im away. I guess this is only doable for 3.3? Anything we can do to help in 3.2 that havent already been done ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8301?page=com.atlassian.jira.plugin... ] Libor Zoubek closed JBIDE-8301. ------------------------------- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira