Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-2061

CLI fails to show app status when runtime-name is different from the deployment name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 8.0.0.Final
    • 8.0.0.Alpha4
    • Management
    • None
    • Hide

      Step1). Deploy an application with a different --name and --runtime-name as following:

      [domain@localhost:9999 /] deploy /home/ABC.ear --name=ABC.ear --runtime-name=XYZ.ear --server-groups=main-server-group

      Step2). Now try to see the status of an application then it is showing "no metrics available".

      [domain@localhost:9999 /] /host=master/server=server-one/deployment=ABC.ear:read-attribute(name=status)
      {
      "outcome" => "success",
      "result" => "no metrics available"
      }

      Where as if the --name and the --runtime-name is dame then the application status is shown properly as "OK"

      Show
      Step1). Deploy an application with a different --name and --runtime-name as following: [domain@localhost:9999 /] deploy /home/ABC.ear --name=ABC.ear --runtime-name=XYZ.ear --server-groups=main-server-group Step2). Now try to see the status of an application then it is showing "no metrics available". [domain@localhost:9999 /] /host=master/server=server-one/deployment=ABC.ear:read-attribute(name=status) { "outcome" => "success", "result" => "no metrics available" } Where as if the --name and the --runtime-name is dame then the application status is shown properly as "OK"
    • Workaround Exists
    • Hide

      Keep the --runtime-name and --name of the application same at the time of deployment.

      Show
      Keep the --runtime-name and --name of the application same at the time of deployment.

      If an application is deployed with a different "runtime-name" other than the actual EAR "name" then CLI fails to show the Status of the application.

              bstansbe@redhat.com Brian Stansberry
              jaysensharma Jay SenSharma (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: