Description of problem: ================== 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. Version-Release number of selected component (if applicable): How reproducible: Yes Steps to Reproduce: ================== 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" } Actual results: =============== Where as if the --name and the --runtime-name is dame then the application status is shown properly as "OK" Expected results: =============== { "outcome" => "success", "result" => "OK" } Additional info:
- According to the "runtime-name" description the users should be allowed to choose a different runtime-name for their deployments. - "description" => "Name by which the deployment should be known within a server's runtime. This would be equivalent to the file name of a deployment file, and would form the basis for such things as default Java Enterprise Edition application and module names. This would typically be the same as 'name', but in some cases users may wish to have two deployments with the same 'runtime-name' (e.g. two versions of \"foo.war\") both available in the deployment content repository, in which case the deployments would need to have distinct 'name' values but would have the same 'runtime-name'."
Karsten Jorgensen <karjoe> made a comment on jira WFLY-2061 If the "name" is not identical to the "runtime-name", it is also not possible to check statistics like the number of instances of some session bean. I don't know if the root cause of this is the same as the root cause of not being able to check the application status?
Verified with 6.2.1.CP.CR1-patch.