Bug 865735

Summary: [HTTP Connectors Load Balancing Guide]: rename parameter domain -> loadBalancingGroup
Product: [JBoss] JBoss Enterprise Web Server 2 Reporter: Jan Stefl <jstefl>
Component: doc-HTTP-Connectors-GuideAssignee: Misha H. Ali <mhusnain>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.0.0   
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: 2012-11-08 22:10:26 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:

Description Jan Stefl 2012-10-12 09:29:51 UTC
http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_Web_Server/2/html-single/HTTP_Connectors_Load_Balancing_Guide/index.html#Java_Properties_Proxy_Configuration

Table B.1. Proxy Configuration Values for Tomcat

rename parameter domain -> loadBalancingGroup

Comment 1 Misha H. Ali 2012-10-12 10:43:08 UTC
Fixed.

Comment 2 Misha H. Ali 2012-10-12 22:56:55 UTC
Available for verification at the same link as reporter comment.

Comment 3 Jan Stefl 2012-10-15 07:14:48 UTC
Please do do changes even in description (same row as previous + in table Table B.2. Proxy Configuration Values for JBoss Enterprise Application Platform 6)


domain -> loadBalancingGroup

Comment 4 Misha H. Ali 2012-10-16 00:59:08 UTC
Fixed descriptions in both tables. This bug will be set to ON_QA once the changes appear on the stage.

Comment 6 Jan Stefl 2012-10-16 07:37:59 UTC
Thanks.
I have last thing. Please add smt. like following to previously updated rows.

"NOTE: Tomcat from EWS2 doesn't support clustering"

It will be last thing from this.
Thanks for patience.

Comment 8 Jan Stefl 2012-10-17 08:41:43 UTC
Great, thank you.

Comment 9 Misha H. Ali 2012-11-08 22:10:26 UTC
This bug is set to CLOSED CURRENT RELEASE to indicate that this fix is now released and available at access.redhat.com.