Bug 1014078 - Missing socket-binding-group as mandatory argument for server group
Summary: Missing socket-binding-group as mandatory argument for server group
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: EAP 6.3.0
Assignee: Misha H. Ali
QA Contact: Russell Dickenson
URL: http://documentation-devel.engineerin...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-01 11:38 UTC by Petr Kremensky
Modified: 2014-08-14 15:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 14874, Administration and Configuration Guide-6.2-1 Build Date: 18-09-2013 13:43:23 Topic ID: 3605-385432 [Latest]
Last Closed: 2014-06-28 15:25:28 UTC
Type: Bug


Attachments (Terms of Use)

Description Petr Kremensky 2013-10-01 11:38:18 UTC
Title: About Server Groups

Describe the issue:
There is only "name" and "profile" mentioned among mandatory attributes, but also "socket-binding-group" is mandatory for server group.

Suggestions for improvement:
Move "socket-binding-group" to mandatory attributes and remove "If the socket-binding-group name is not provided in the server-group element, it must be provided for each server in the host.xml." part from it.

Additional information:
EAP 6.2.0
http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6.2/html/Administration_and_Configuration_Guide/Server_Groups.html

Comment 2 Scott Mumford 2014-02-26 05:14:19 UTC
Moving to ON_QA.

The changes should be available for review on the documentation stage within an hour or so from this comment.

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/

Comment 3 Scott Mumford 2014-02-26 05:16:02 UTC
Moving to ON_QA.

The changes should be available for review on the documentation stage within an hour or so from this comment.

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/

Comment 4 Petr Kremensky 2014-02-26 07:56:35 UTC
There is still "If the socket-binding-group name is not provided in the server-group element, it must be provided for each server in host.xml." part. It is true that socket-binding-group can be overridden on a per-server basis in host.xml, but it is mandatory element for every server group. If the socket-binding-group element is missing in server-group configuration, domain fails to start.

Comment 6 Petr Kremensky 2014-02-27 09:59:36 UTC
This is still not correct :). Please fix it in following manner:

socket-binding-group: the default socket binding group used for servers in the group. This name can be overridden on a per-server basis in host.xml, but it is a mandatory element for every server-group and the domain can not start if it is missing.

Last sentence "If the socket-binding-group name..." makes no sense as if the socket-binding-group is not provided, domain won't start.

To make it clear you can specify the socket-binding-group in two places
a) server-group
b) server

 - each server belongs to some server-group.
 - socket-binding-group is mandatory element for each server group
 - by specifying socket-binding-group for server you can actually overwrite the value specified in server-group (on a per-server basis), but even if you overwrite this value, it must still be present in server-group configuration or domain won't start

Comment 7 Misha H. Ali 2014-02-27 11:18:22 UTC
I see. thank you for the explanation, Petr. I've removed the last line altogether since it does in fact not make sense and we already convey the fact that we can override the server group setting for individual hosts earlier.

Hopefully this is OK now.

Comment 8 Russell Dickenson 2014-03-10 22:29:25 UTC
The amended text is now available for review in revision 6.3.0-3 (or higher) at [1].


[1] http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Administration_and_Configuration_Guide/index.html#Server_Groups

Comment 9 Petr Kremensky 2014-03-11 06:52:25 UTC
Verified during EAP 6.3.0.DR2 testing cycle.


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