[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8301) Not clear what Start/Stop actually does for remote servers

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583656#comment-12583656 ] 

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. 

> Not clear what Start/Stop actually does for remote servers
> ----------------------------------------------------------
>
>                 Key: JBIDE-8301
>                 URL: https://issues.jboss.org/browse/JBIDE-8301
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 3.2.1
>
>
> when starting/stopping remote servers its not really clear what is going on - i.e. what is the semantics when stopping  a server that were already running when started ?
> Does it execute a command or does it just disconnect ?
> For example right now when I try and stop a server it keeps coming back saying "Server jboss-eap remote failed to stop." and it still says "Started". How do I actually make the server adapter think the server has stopped so it doesn't keep deploying to it withuot having to restart eclipse.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira