Bug 814312

Summary:	[as7] Describe jvm child handling on server-group and managed server level
Product:	[Other] RHQ Project	Reporter:	Heiko W. Rupp <hrupp>
Component:	Documentation	Assignee:	Deon Ballard <dlackey>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	4.3	CC:	hrupp
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:	2013-09-01 19:19:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	707223

Description Heiko W. Rupp 2012-04-19 14:56:26 UTC

(from Bug 813214 )

The resource type of "JVM Definition" for server-groups (SG) and managed
servers (MS) are singletons below the level of managed server or server group. 
This means that a MS or SG can only have one child of that type. Unfortunately
the UI allows to create as many singleton resources of a type as the user wants
( Bug 814305 )

The name of the resource must be one of the jvm definitions at host level.
Unfortunately the UI does not allow for pre-computed names (see Bug 814309 ) so
the user can enter any name at the wizard. On the properties page he gets the
list of allowed base definitions that are then turned into the final name. 

When the user has submitted the resource creation request and another resource
of this type exists already, an Excption is thrown saying that this is a
singleton and that he should delete the other resource first.

Comment 1 Deon Ballard 2012-06-28 17:52:16 UTC

This is mentioned in the EAP 6 docs:
http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.1/html/How_to_Manage_JBoss_Servers/eap6-jvm.html

And in the release notes:
http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.1/html/3.1_Release_Notes/Known-Issues-with-this-release.html#known-issues-eap6

Comment 2 Heiko W. Rupp 2013-09-01 19:19:18 UTC

Bulk closing of BZs that have no target version set, but which are ON_QA for more than a year and thus are in production for a long time.