Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-11825

Remote server marked as started even if start failed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 3.3.0.CR1
    • 3.3.0.Beta3
    • server
    • None
    • Hide

      1. Set up remote AS7 server
      2. Make sure some of the parameters prevent the server from starting correctly

      • in current builds you don't have to do anything - JBIDE-11824 will break it for you
      • otherwise:
        2.1 Open the server in server editor
        2.2 Open launch configuration
        2.3 Modify the start command to break the launch - e.g. change server config to null (--server-config=null)
        3. Start the server
        4. The server will eventually change to Started in server view but in fact no java process will be running on the remote system - FAIL
      Show
      1. Set up remote AS7 server 2. Make sure some of the parameters prevent the server from starting correctly in current builds you don't have to do anything - JBIDE-11824 will break it for you otherwise: 2.1 Open the server in server editor 2.2 Open launch configuration 2.3 Modify the start command to break the launch - e.g. change server config to null (--server-config=null) 3. Start the server 4. The server will eventually change to Started in server view but in fact no java process will be running on the remote system - FAIL

      When a remote AS7 fails to start (e.g. because of JBIDE-11824) and the process on the remote server stops immediately AS tooling still marks it as Started in server view. I think it is not acceptable to do that. Started should really mean started.

            rob.stryker Rob Stryker (Inactive)
            exd-mmalina Martin Malina
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: