19.5.4. Install the mod_cluster Module Into Apache HTTP Server or JBoss Enterprise Web Server (RPM)
Describe the issue:
- To have the Apache HTTP Server service start at boot, enter the following command:
- Start the mod_cluster balancer with the following command:
Please, add update (information bubble perhaps...) for RHEL7 accordingly to BZ 1126030.
The installation procedure, i.e.
yum install mod_cluster-native
remains _exactly_ the same on RHEL7, so this is O.K.
RHEL5 - Customer must use our EAP6 httpd package, the operation system one is not supported.
RHEL6 - Customer can choose between httpd package from EAP6 distribution of the operation system one.
RHEL7 - Customer must use our EAP6 httpd22 package, the operating system one is not supported.
I'm sorry, I forgot to mention one very important thing in the description:
One has to enable UDP port in firewalld in order to allow advertising messages:
firewall-cmd --permanent --zone=public --add-port=23364/udp
The same issue is already addressed for IPtables on RHEL5/6 and for Windows firewall in the documentation. This amendment is for RHEL7 and firewalld only.
Note: 18.104.22.168:23364 is the default address and port for mod_cluster balancer advertising UDP multicast.
Michal, I am not clear which topic your comment 2 refers to. Can you clarify where this belongs?
Spoke with Michal. He suggested the content in comment 2 belongs with the other firewall content in topic 4705. Updated topic:
Configure Network Firewalls to Work with JBoss EAP 6 [4705, rev: 690288]
This can be verified at the following links:
I'm sorry, there are superfluous statements about RHEL7 that suggest one might use mod_cluster with Apache HTTP Server from RHEL7, which is not true, see the Description.
To perform this task, you must be using the Apache HTTP Server installed in Red Hat Enterprise Linux 6 or 7, JBoss Enterprise Web Server, or the standalone Apache HTTP Server included as a separate downloadable component of JBoss EAP 6.
This is wrong, the old version was O.K. and no change was requested:
To perform this task, you must be using the Apache HTTP Server installed in Red Hat Enterprise Linux 6, JBoss Enterprise Web Server, or the standalone Apache HTTP Server included as a separate downloadable component of JBoss EAP 6.
Please see the Description of this Bugzilla, Section Summary. RHEL 7 Apache HTTP Server is _not_ supported with EAP6 mod_cluster. Customer must use the Apache HTTP Server distributed with EAP6.
If you need to install Apache HTTP Server in Red Hat Enterprise Linux 6 or 7, use the instructions from the Red Hat Enterprise Linux 6 Deployment Guide.
Again, please, remove the reference to "7". It was not requested and it's actually wrong. EAP6 mod_cluster does not support RHEL 7 Apache HTTP Server, as it's depicted in the Description of this Bugzilla.
The rest of the content looks great and makes sense for RHEL7 installation, including all the new commands and service control. The firewall settings are O.K. as well.
As soon as you remove the two aforementioned RHEL7 references, we are good to go.
Thank you very much for this last-minute effort.
I'm removing the blocker flag, because we have the following statement in the Release notes :
mod_jk and mod_cluster with Apache on RHEL 7
The Apache HTTP server installable on Red Hat Enterprise Linux 7 via RHN
channels introduces incompatibility problems with mod_cluster and mod_jk
and is not supported. The Apache HTTP server shipped with JBoss EAP,
however, is fully supported.
So in my opinion, the reader will be aware of the fact that we don't support it. If you don't share my view, please, return the blocker flag back.
I removed the RHEL 7 reference from the topic and updated the spec for the Administration and Configuration Guide  with the current rev:
Install the mod_cluster Module Into Apache HTTP Server or JBoss Enterprise Web Server (RPM) [24378, rev: 690666]
I did NOT rebuild the guide because Michal removed the blocker flag. If we do decide to update the guides in the near future, the topic will be correct.
Change target to 6.3.0 post-GA.
This can be verified on DocStage here:
Verified in 6.3.0-44 revision