Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1049102 - [GSS] (6.3) CLI fails to show app status when runtime-name is different from the deployment name
[GSS] (6.3) CLI fails to show app status when runtime-name is different from ...
Status: CLOSED CURRENTRELEASE
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management (Show other bugs)
6.0.1
All All
unspecified Severity medium
: DR0
: EAP 6.3.0
Assigned To: Brian Stansberry
Petr Kremensky
Russell Dickenson
:
Depends On:
Blocks: 1007696
  Show dependency treegraph
 
Reported: 2014-01-06 21:21 EST by Brian Stansberry
Modified: 2014-06-30 10:58 EDT (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In previous versions of JBoss EAP 6, the management operation handler used to determine the status of a deployment was using the deployment name to find the deployment service instead of using its runtime-name. As a result, if a deployment had a runtime-name that was different from its management name, an attempt to read its "status" attribute would result in a response of `No metrics available`. For example: ---- [standalone@localhost:9999 /] deploy /home/ABC.ear --name=ABC.ear --runtime-name=XYZ.ear [standalone@localhost:9999 /] /deployment=ABC.ear:read-attribute(name=status) { "outcome" => "success", "result" => "no metrics available" } ---- In this release of the product, the management handler uses the runtime-name when looking up the deployment service which ensures the status is correctly returned. The response from the above example is now: ---- [standalone@localhost:9999 /] /deployment=ABC.ear:read-attribute(name=status) { "outcome" => "success", "result" => "OK" } ----
Story Points: ---
Clone Of: 1007696
Environment:
Last Closed: 2014-06-28 11:31:40 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker WFLY-2061 Major Resolved CLI fails to show app status when runtime-name is different from the deployment name 2017-06-27 07:27 EDT

  None (edit)
Comment 3 Petr Kremensky 2014-02-24 09:45:47 EST
Verified on EAP 6.3.0.DR0.

Note You need to log in before you can comment on or make changes to this bug.