Bug 825127

Summary: [eap6] platform-mbean resource for Managed server
Product: [Other] RHQ Project Reporter: Libor Zoubek <lzoubek>
Component: PluginsAssignee: RHQ Project Maintainer <rhq-maint>
Status: NEW --- QA Contact: Mike Foley <mfoley>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.4CC: hrupp, theute
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Bug Depends On:    
Bug Blocks: 707223    

Description Libor Zoubek 2012-05-25 04:04:16 EDT
Description of problem: For a standalone server there is a resource called platform-mbean that provides information about underlying JVM. For a managed server there is same resource, but its name is called 'host=master,server=server-one,core-service=platform-mbean' which equals its path in connection settings.


Version-Release number of selected component (if applicable):
JON 3.1.ER4 EAP6.ER8

How reproducible:always

Expected results: JVM resource for managed server should be called 'platform-mbean' as well
Comment 1 Heiko W. Rupp 2012-05-25 11:51:22 EDT
[17:48:02] <pilhuhn> This is the display name that the user could change in the UI - so if we change that later, the resource would stay, but changes of the user would be overwritten
[17:48:39] <pilhuhn> Changing the discovery code for this one special case looks more dangerous to me
[17:49:12] <pilhuhn> We could subclass the normal discovery perhaps and change the name though  that would be a relatively safe change
[17:50:08] <ccrouch> we could fix the discovery code 
[17:50:18] <ccrouch> and that won't impact user changed values right
[17:50:25] <pilhuhn> Right