Bug 825127 - [eap6] platform-mbean resource for Managed server
Summary: [eap6] platform-mbean resource for Managed server
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: as7-plugin
TreeView+ depends on / blocked
 
Reported: 2012-05-25 08:04 UTC by Libor Zoubek
Modified: 2022-03-31 04:28 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Libor Zoubek 2012-05-25 08:04:16 UTC
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 15:51:22 UTC
[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


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