Bug 730772

Summary: AS7 Plugigin, Failed to load group composite modifying SocketBindingGroup
Product: [Other] RHQ Project Reporter: Mike Foley <mfoley>
Component: PluginsAssignee: Mike Foley <mfoley>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.1CC: hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-07 19:28:04 UTC Type: ---
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    
Attachments:
Description Flags
image 1 of the error
none
error from the message center none

Description Mike Foley 2011-08-15 17:56:05 UTC
Created attachment 518301 [details]
image 1 of the error

Description of problem:  AS7 Plugigin, Failed to load group composite modifying SocketBindingGroup


Version-Release number of selected component (if applicable):
AS7 Final, RHQ 8/15 build

How reproducible:
100%

Steps to Reproduce:
1.  Inventory-->Platform-->your platform-->JBossAS7-Standalone-->SocketBindingGroupStandalone
2.  change port offset, type in "1" or something 
3.  click save, observe error  (see attached image, there is no server-side error message)
  
Actual results:


Expected results:


Additional info:

Comment 1 Mike Foley 2011-08-15 17:56:34 UTC
Created attachment 518302 [details]
error from the message center

Comment 2 Heiko W. Rupp 2011-08-16 13:16:34 UTC
Can not reproduce.
Also note that the issue seem to be *group* related (check e.g. the text on socketbindingexception2.png) and not single resource as described in the steps above

Comment 3 Mike Foley 2011-08-17 19:22:06 UTC
verified as follows:
1) updating config property for port offset on the resource, OK
2) updating config property for port offset on the group ... received a warning.  assuming that is the correct behavior ... much better than the error and the message center.

Comment 4 Mike Foley 2012-02-07 19:28:04 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE