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

Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • 4.3.0.Alpha2
    • 4.2.2.Final
    • server
    • None
    • Hide

      1. EXEC: Open New Server wizard via context menu in Servers view
      2. EXEC: Select OpenShift - OpenShift Server Adapter
      3. EXEC: Select WildFly 8.x server and proceed through wizard.
      4. ASSERT: Server has been creted.
      5. EXEC: Start server

      RESULT: Warning that there is a server running on 8080 is shown.
      EXPECTED RESULT: Server is started.

      Show
      1. EXEC: Open New Server wizard via context menu in Servers view 2. EXEC: Select OpenShift - OpenShift Server Adapter 3. EXEC: Select WildFly 8.x server and proceed through wizard. 4. ASSERT: Server has been creted. 5. EXEC: Start server RESULT: Warning that there is a server running on 8080 is shown. EXPECTED RESULT: Server is started.

      If I am creating new server in Servers view via New Server wizard and I select in tree at first OpenShift Server Adapter and then e.g. Wildfly 8.x server, then created server cannot be started. There is a warning there there is server running on openshift.redhat.com:8080. User has to delete such server from servers view and create a new one without selecting OpenShift Server Adapter in server type selection.

        1. JBIDE-19108_1.png
          JBIDE-19108_1.png
          45 kB
        2. JBIDE-19108_2.png
          JBIDE-19108_2.png
          47 kB
        3. JBIDE-19108_3.png
          JBIDE-19108_3.png
          46 kB
        4. server_already_running.png
          server_already_running.png
          36 kB

            rob.stryker Rob Stryker (Inactive)
            mlabuda_jira Marián Labuda (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: