Bug 730772 - AS7 Plugigin, Failed to load group composite modifying SocketBindingGroup
Summary: AS7 Plugigin, Failed to load group composite modifying SocketBindingGroup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 4.1
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Mike Foley
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: as7-plugin
TreeView+ depends on / blocked
 
Reported: 2011-08-15 17:56 UTC by Mike Foley
Modified: 2012-02-07 19:28 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-02-07 19:28:04 UTC
Embargoed:


Attachments (Terms of Use)
image 1 of the error (51.29 KB, image/png)
2011-08-15 17:56 UTC, Mike Foley
no flags Details
error from the message center (16.47 KB, image/png)
2011-08-15 17:56 UTC, Mike Foley
no flags Details

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


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