I believe this is a fault on Red Hat's end. They appear to have two packages named "mod_cluster", one which is part of Apache and one that is part of JBoss (which is just an alias for mod_cluster-native?):
mod_cluster.noarch : JBoss mod_cluster for Apache httpd
mod_cluster-demo.noarch : Sample app for mod_cluster
mod_cluster-native.x86_64 : JBoss mod_cluster for Apache httpd
mod_cluster.x86_64 : Apache HTTP load balancer
"yum groupinstall 'JBoss EAP 6'" is supposed to installed mod_cluster.noarch, not mod_cluster.x86_64.
'rpm -ql' results from this broken system, and the same from a system that works:
# rpm -ql mod_cluster
/etc/httpd/conf.d/mod_cluster.conf
/usr/lib64/httpd/modules/mod_advertise.so
/usr/lib64/httpd/modules/mod_manager.so
/usr/lib64/httpd/modules/mod_proxy_cluster.so
/usr/lib64/httpd/modules/mod_slotmem.so
/usr/share/doc/mod_cluster-1.2.6
/usr/share/doc/mod_cluster-1.2.6/README
/usr/share/doc/mod_cluster-1.2.6/lgpl.txt
# rpm -ql mod_cluster
/etc/maven/fragments/mod_cluster
/usr/share/java/mod_cluster-container-catalina-1.2.6.Final-redhat-1-sources.jar
/usr/share/java/mod_cluster-container-catalina-1.2.6.Final-redhat-1.jar
/usr/share/java/mod_cluster-container-catalina-sources.jar
/usr/share/java/mod_cluster-container-catalina-standalone-1.2.6.Final-redhat-1-sources.jar
/usr/share/java/mod_cluster-container-catalina-standalone-1.2.6.Final-redhat-1.jar
/usr/share/java/mod_cluster-container-catalina-standalone-sources.jar
/usr/share/java/mod_cluster-container-catalina-standalone.jar
/usr/share/java/mod_cluster-container-catalina.jar
/usr/share/java/mod_cluster-container-jbossweb-1.2.6.Final-redhat-1-sources.jar
/usr/share/java/mod_cluster-container-jbossweb-1.2.6.Final-redhat-1.jar
/usr/share/java/mod_cluster-container-jbossweb-sources.jar
/usr/share/java/mod_cluster-container-jbossweb.jar
/usr/share/java/mod_cluster-container-spi-1.2.6.Final-redhat-1-sources.jar
/usr/share/java/mod_cluster-container-spi-1.2.6.Final-redhat-1.jar
/usr/share/java/mod_cluster-container-spi-sources.jar
/usr/share/java/mod_cluster-container-spi.jar
/usr/share/java/mod_cluster-container-tomcat6-1.2.6.Final-redhat-1-sources.jar
/usr/share/java/mod_cluster-container-tomcat6-1.2.6.Final-redhat-1.jar
/usr/share/java/mod_cluster-container-tomcat6-sources.jar
/usr/share/java/mod_cluster-container-tomcat6.jar
/usr/share/java/mod_cluster-container-tomcat7-1.2.6.Final-redhat-1-sources.jar
/usr/share/java/mod_cluster-container-tomcat7-1.2.6.Final-redhat-1.jar
/usr/share/java/mod_cluster-container-tomcat7-sources.jar
/usr/share/java/mod_cluster-container-tomcat7.jar
/usr/share/java/mod_cluster-core-1.2.6.Final-redhat-1-sources.jar
/usr/share/java/mod_cluster-core-1.2.6.Final-redhat-1.jar
/usr/share/java/mod_cluster-core-sources.jar
/usr/share/java/mod_cluster-core.jar
/usr/share/maven2/poms/JPP-mod_cluster-container-catalina-standalone.pom
/usr/share/maven2/poms/JPP-mod_cluster-container-catalina.pom
/usr/share/maven2/poms/JPP-mod_cluster-container-jbossweb.pom
/usr/share/maven2/poms/JPP-mod_cluster-container-spi.pom
/usr/share/maven2/poms/JPP-mod_cluster-container-tomcat6.pom
/usr/share/maven2/poms/JPP-mod_cluster-container-tomcat7.pom
/usr/share/maven2/poms/JPP-mod_cluster-container.pom
/usr/share/maven2/poms/JPP-mod_cluster-core.pom
/usr/share/maven2/poms/JPP-mod_cluster-parent.pom
Background:
Two RHEL 6.5 VMs were built to run JBoss EAP in Domain mode, one system as a domain controller / master and the other as slave. These systems are working fine.
A third VM was added to function as a second slave. The template used to install this system was different from that used for the first two. In particular, the template used for this system included the "epel" (Fedora) repo. The two other VMs do not have this repo.
In all cases JBoss was installed as follows:
# yum groupinstall "JBoss EAP 6"
This groupinstall will install the package "mod_cluster". The epel repo has a mod_cluster package (mod_cluster.x86_64) that conflicts with the mod_cluster package in the JBoss EAP repo (jb-eap-6-for-rhel-6-server-rpms - mod_cluster.noarch / mod_cluster-native.x86_64).
Removing the epel repo solves the issue. In my case, I had the third VM rebuilt to match the first two.