jboss domain&cluster 配置

1，在JBOSS wildfly-8.2.1.Final启动过程中 会报出一个警告信息；

In wildfly,In the process of loading

WARN [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.

修改standalone.xml 在

<subsystem xmlns="urn:jboss:domain:transactions:2.0">

下增加

node-identifier="${jboss.node.name}"

Modify the standalone.xml,Add child nodes --node-identifier.

<subsystem xmlns="urn:jboss:domain:transactions:2.0">
<core-environment node-identifier="${jboss.node.name}">
<process-id>
<uuid/>
</process-id>
</core-environment>
<recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
</subsystem>

如果早domain模式下报此错误，就将整个domain 文件中的此部分更改；

2，配置域模式下的jboss

测试环境说明

JBOSS :wildfly-8.2.1.Final.tar.gz

FQDN                            IP                                ROLE            INSTANCE                        MARK
hnxz-vm-mysql-p01        10.207.238.66                           MASTER         server-m8080
server-m8081
server-m8082
hnxz-vm-mysql-S01        10.207.238.67                           SLAVE          server-s8080
server-s8081
server-s8082

master需要修改之文件主要有两个domain.xml,host.xml

a,首先建立管理员帐号root,slave

建立应用账号app

建立账号输出的密码部分一定要保存下来，后面的配置文件会用到；

“Y2lzY28sLDE5ODk=”

[root@hnxz-vm-mysql-p01 wildfly-8.2.1.Final]# ./bin/add-user.sh

b,修改master 主机host.xml

<host name="master" xmlns="urn:jboss:domain:2.2">

<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:10.207.238.66}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:10.207.238.66}"/>
</interface>
<interface name="unsecure">
<inet-address value="${jboss.bind.address.unsecure:10.207.238.66}"/>
</interface>
</interfaces>

c,修改后以domain模式启动jboss 使用浏览器登录http://10.207.238.66:9990/ 用户名密码为刚建立之root账密

登录后将默认之server删除，建立如下的server 注意：删除server时一定将servers stop后再删除；

stop server界面



添加完服务器后界面：



mater 主机 host.xml文件全文如下：

<?xml version='1.0' encoding='UTF-8'?>
<host name="master" xmlns="urn:jboss:domain:2.2">
<management>
<security-realms>
<security-realm name="ManagementRealm">
<authentication>
<local default-user="$local" skip-group-loading="true"/>
<properties path="mgmt-users.properties" relative-to="jboss.domain.config.dir"/>
</authentication>
<authorization map-groups-to-roles="false">
<properties path="mgmt-groups.properties" relative-to="jboss.domain.config.dir"/>
</authorization>
</security-realm>
<security-realm name="ApplicationRealm">
<authentication>
<local default-user="$local" allowed-users="*" skip-group-loading="true"/>
<properties path="application-users.properties" relative-to="jboss.domain.config.dir"/>
</authentication>
<authorization>
<properties path="application-roles.properties" relative-to="jboss.domain.config.dir"/>
</authorization>
</security-realm>
</security-realms>
<audit-log>
<formatters>
<json-formatter name="json-formatter"/>
</formatters>
<handlers>
<file-handler name="host-file" formatter="json-formatter" path="audit-log.log" relative-to="jboss.domain.data.dir"/>
<file-handler name="server-file" formatter="json-formatter" path="audit-log.log" relative-to="jboss.server.data.dir"/>
</handlers>
<logger log-boot="true" log-read-only="false" enabled="false">
<handlers>
<handler name="host-file"/>
</handlers>
</logger>
<server-logger log-boot="true" log-read-only="false" enabled="false">
<handlers>
<handler name="server-file"/>
</handlers>
</server-logger>
</audit-log>
<management-interfaces>
<native-interface security-realm="ManagementRealm">
<socket interface="management" port="${jboss.management.native.port:9999}"/>
</native-interface>
<http-interface security-realm="ManagementRealm" http-upgrade-enabled="true">
<socket interface="management" port="${jboss.management.http.port:9990}"/>
</http-interface>
</management-interfaces>
</management>
<domain-controller>
<local/>
</domain-controller>
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:10.207.238.66}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:10.207.238.66}"/>
</interface>
<interface name="unsecure">
<inet-address value="${jboss.bind.address.unsecure:10.207.238.66}"/>
</interface>
</interfaces>
<jvms>
<jvm name="default">
<heap size="64m" max-size="256m"/>
<permgen size="256m" max-size="256m"/>
<jvm-options>
<option value="-server"/>
</jvm-options>
</jvm>
</jvms>
<servers>
<server name="server-m8080" group="main-server-group" auto-start="true">
<socket-bindings socket-binding-group="full-ha-sockets" port-offset="0"/>
</server>
<server name="server-m8081" group="main-server-group" auto-start="true">
<socket-bindings socket-binding-group="full-ha-sockets" port-offset="1"/>
</server>
<server name="server-m8082" group="main-server-group" auto-start="true">
<socket-bindings socket-binding-group="full-ha-sockets" port-offset="2"/>
</server>
</servers>
</host>

添加完需要的server后 接下来更改slave host.xml&domain.xml 文件；

2，修改slave host.xml 文件

a,因slave是作为成员加入master所以此处可以将domain.xml文件改名，不使用domain.xml文件

b,host.xml文件修改以下地方，

[root@hnxz-vm-mysql-p02 configuration]# cp -a host-slave.xml host.xml

vim host.xml

<host name="slave" xmlns="urn:jboss:domain:2.2">

这里的host name 为在maste 中建立的账号slave 必须同名；

<server-identities>
<secret value="Y2lzY28sLDE5ODk="/>
</server-identities>

此处的密码为上面slave 账号密码，为上面输出的加密密码

<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:10.207.238.67}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:10.207.238.67}"/>
</interface>
<interface name="unsecure">
<inet-address value="${jboss.bind.address.unsecure:10.207.238.67}"/>
</interface>
</interfaces>

修改127.0.0.1IP地址为主机真实地址10.20.238.67

<domain-controller>
<remote host="${jboss.domain.master.address:10.207.238.66}" port="${jboss.domain.master.port:9999}" security-realm="ManagementRealm"/>
</domain-controller>

更改默认地址指向mater主机也就是controller主机

<servers>
<server name="server-s8080" group="main-server-group"/>
<server name="server-s8081" group="main-server-group" auto-start="true">
<socket-bindings socket-binding-group="full-ha-sockets" port-offset="1"/>
</server>
<server name="server-s8082" group="main-server-group" auto-start="true">
<socket-bindings socket-binding-group="full-ha-sockets" port-offset="2"/>
</server>
</servers>

第一次只需要增加一台server server-s8080 group 为在master主机中的group

<security-realms>
<security-realm name="ManagementRealm">
<server-identities>
<secret value="Y2lzY28sLDE5ODk="/>
</server-identities>
<authentication>
<local default-user="$local" skip-group-loading="true"/>
<properties path="mgmt-users.properties" relative-to="jboss.domain.config.dir"/>
</authentication>
<authorization map-groups-to-roles="false">
<properties path="mgmt-groups.properties" relative-to="jboss.domain.config.dir"/>
</authorization>
</security-realm>
<security-realm name="ApplicationRealm">
<authentication>
<local default-user="$local" allowed-users="*" skip-group-loading="true"/>
<properties path="application-users.properties" relative-to="jboss.domain.config.dir"/>
</authentication>
<authorization>
<properties path="application-roles.properties" relative-to="jboss.domain.config.dir"/>
</authorization>
</security-realm>
</security-realms>

以上内容需要高度重要，为master 与slave的认证部分；

我们需要做一下slave对master的认证连接工作。slave要想和master建立域控关系，需要知道master的管理端账号密码。在域控这一块，AS8（wildfly）对认证有要求：需要在域控制器上以过来连接的主机host名为用户名添加账号。

slave 主机 host.xml文件全文如下：

<?xml version='1.0' encoding='UTF-8'?>
<host name="slave" xmlns="urn:jboss:domain:2.2">
<management>
<security-realms>
<security-realm name="ManagementRealm">
<server-identities>
<secret value="Y2lzY28sLDE5ODk="/>
</server-identities>
<authentication>
<local default-user="$local" skip-group-loading="true"/>
<properties path="mgmt-users.properties" relative-to="jboss.domain.config.dir"/>
</authentication>
<authorization map-groups-to-roles="false">
<properties path="mgmt-groups.properties" relative-to="jboss.domain.config.dir"/>
</authorization>
</security-realm>
<security-realm name="ApplicationRealm">
<authentication>
<local default-user="$local" allowed-users="*" skip-group-loading="true"/>
<properties path="application-users.properties" relative-to="jboss.domain.config.dir"/>
</authentication>
<authorization>
<properties path="application-roles.properties" relative-to="jboss.domain.config.dir"/>
</authorization>
</security-realm>
</security-realms>
<audit-log>
<formatters>
<json-formatter name="json-formatter"/>
</formatters>
<handlers>
<file-handler name="host-file" formatter="json-formatter" path="audit-log.log" relative-to="jboss.domain.data.dir"/>
<file-handler name="server-file" formatter="json-formatter" path="audit-log.log" relative-to="jboss.server.data.dir"/>
</handlers>
<logger log-boot="true" log-read-only="false" enabled="false">
<handlers>
<handler name="host-file"/>
</handlers>
</logger>
<server-logger log-boot="true" log-read-only="false" enabled="false">
<handlers>
<handler name="server-file"/>
</handlers>
</server-logger>
</audit-log>
<management-interfaces>
<native-interface security-realm="ManagementRealm">
<socket interface="management" port="${jboss.management.native.port:9999}"/>
</native-interface>
</management-interfaces>
</management>
<domain-controller>
<remote host="${jboss.domain.master.address:10.207.238.66}" port="${jboss.domain.master.port:9999}" security-realm="ManagementRealm"/>
</domain-controller>
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:10.207.238.67}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:10.207.238.67}"/>
</interface>
<interface name="unsecure">
<inet-address value="${jboss.bind.address.unsecure:10.207.238.67}"/>
</interface>
</interfaces>
<jvms>
<jvm name="default">
<heap size="64m" max-size="256m"/>
<permgen size="256m" max-size="256m"/>
<jvm-options>
<option value="-server"/>
</jvm-options>
</jvm>
</jvms>
<servers>
<server name="server-s8080" group="main-server-group"/>
<server name="server-s8081" group="main-server-group" auto-start="true">
<socket-bindings socket-binding-group="full-ha-sockets" port-offset="1"/>
</server>
<server name="server-s8082" group="main-server-group" auto-start="true">
<socket-bindings socket-binding-group="full-ha-sockets" port-offset="2"/>
</server>
</servers>
</host>

3,将master slave 分别以domain模式启动，进入控制台观察是否运行正常；

4,jboss 集群的安装

a,集群的安装需要用到以上domain 的配置，也就是需要先配置好domain然后再配置域；

b,从官网下载binary文件

http://mod-cluster.jboss.org/mod_cluster/downloads/1-2-6-Final-bin

下载相应的linux版本文件，将其安装在master 主机上，确保master 主机的80端口没有被占用；

c,解压相应的压缩包文件

tar -zxvf mod_cluster-1.2.6.Final-linux2-x64-ssl.tar.gz -C /

d,修改httpd.conf文件

[root@hnxz-vm-mysql-p01 conf]# pwd
/opt/jboss/httpd/httpd/conf
[root@hnxz-vm-mysql-p01 conf]# vim httpd.conf

#Listen 12.34.56.78:80
Listen 80

40行，把原来的端口8000，改成80，这样方便直接用 http://172.21.129.181/xxx 来访问应用

ServerName 172.21.129.181:80

164行改成

最后的mod_cluster部分，参考下面修改

# MOD_CLUSTER_ADDS
# Adjust to you hostname and subnet.
<IfModule manager_module>
Listen 172.21.129.181:6666
ManagerBalancerName mycluster
<VirtualHost 172.21.129.181:6666>
<Location />
Order deny,allow
#Deny from all
Allow from all
</Location>
KeepAliveTimeout 300
MaxKeepAliveRequests 0
#ServerAdvertise on http://127.0.0.1:6666 AdvertiseFrequency 5
#AdvertiseSecurityKey secret
#AdvertiseGroup 224.0.1.105:23364
EnableMCPMReceive
<Location /mod_cluster_manager>
SetHandler mod_cluster-manager
Order deny,allow
#Deny from all
Allow from all
</Location>
</VirtualHost>
</IfModule>

主要是把127.0.0.1，改成master server对应的真实IP，另外把Deny from all注释掉，把紧贴着的一行改成Allow from all，去掉这些访问上的限制；
下面是完整的http.conf参考内容:

#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo_log"
# with ServerRoot set to "/opt/jboss/httpd/httpd" will be interpreted by the
# server as "/opt/jboss/httpd/httpd/logs/foo_log".
#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk.  If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "/opt/jboss/httpd/httpd"
#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80
#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule authn_file_module /opt/jboss/httpd/lib/httpd/modules/mod_authn_file.so
LoadModule authn_dbm_module /opt/jboss/httpd/lib/httpd/modules/mod_authn_dbm.so
LoadModule authn_anon_module /opt/jboss/httpd/lib/httpd/modules/mod_authn_anon.so
LoadModule authn_dbd_module /opt/jboss/httpd/lib/httpd/modules/mod_authn_dbd.so
LoadModule authn_default_module /opt/jboss/httpd/lib/httpd/modules/mod_authn_default.so
LoadModule authn_alias_module /opt/jboss/httpd/lib/httpd/modules/mod_authn_alias.so
LoadModule authz_host_module /opt/jboss/httpd/lib/httpd/modules/mod_authz_host.so
LoadModule authz_groupfile_module /opt/jboss/httpd/lib/httpd/modules/mod_authz_groupfile.so
LoadModule authz_user_module /opt/jboss/httpd/lib/httpd/modules/mod_authz_user.so
LoadModule authz_dbm_module /opt/jboss/httpd/lib/httpd/modules/mod_authz_dbm.so
LoadModule authz_owner_module /opt/jboss/httpd/lib/httpd/modules/mod_authz_owner.so
LoadModule authz_default_module /opt/jboss/httpd/lib/httpd/modules/mod_authz_default.so
LoadModule auth_basic_module /opt/jboss/httpd/lib/httpd/modules/mod_auth_basic.so
LoadModule auth_digest_module /opt/jboss/httpd/lib/httpd/modules/mod_auth_digest.so
LoadModule advertise_module /opt/jboss/httpd/lib/httpd/modules/mod_advertise.so
LoadModule file_cache_module /opt/jboss/httpd/lib/httpd/modules/mod_file_cache.so
LoadModule cache_module /opt/jboss/httpd/lib/httpd/modules/mod_cache.so
LoadModule disk_cache_module /opt/jboss/httpd/lib/httpd/modules/mod_disk_cache.so
LoadModule mem_cache_module /opt/jboss/httpd/lib/httpd/modules/mod_mem_cache.so
LoadModule dbd_module /opt/jboss/httpd/lib/httpd/modules/mod_dbd.so
LoadModule dumpio_module /opt/jboss/httpd/lib/httpd/modules/mod_dumpio.so
LoadModule reqtimeout_module /opt/jboss/httpd/lib/httpd/modules/mod_reqtimeout.so
LoadModule ext_filter_module /opt/jboss/httpd/lib/httpd/modules/mod_ext_filter.so
LoadModule include_module /opt/jboss/httpd/lib/httpd/modules/mod_include.so
LoadModule filter_module /opt/jboss/httpd/lib/httpd/modules/mod_filter.so
LoadModule substitute_module /opt/jboss/httpd/lib/httpd/modules/mod_substitute.so
LoadModule deflate_module /opt/jboss/httpd/lib/httpd/modules/mod_deflate.so
LoadModule log_config_module /opt/jboss/httpd/lib/httpd/modules/mod_log_config.so
LoadModule log_forensic_module /opt/jboss/httpd/lib/httpd/modules/mod_log_forensic.so
LoadModule logio_module /opt/jboss/httpd/lib/httpd/modules/mod_logio.so
LoadModule env_module /opt/jboss/httpd/lib/httpd/modules/mod_env.so
LoadModule mime_magic_module /opt/jboss/httpd/lib/httpd/modules/mod_mime_magic.so
LoadModule cern_meta_module /opt/jboss/httpd/lib/httpd/modules/mod_cern_meta.so
LoadModule expires_module /opt/jboss/httpd/lib/httpd/modules/mod_expires.so
LoadModule headers_module /opt/jboss/httpd/lib/httpd/modules/mod_headers.so
LoadModule ident_module /opt/jboss/httpd/lib/httpd/modules/mod_ident.so
LoadModule usertrack_module /opt/jboss/httpd/lib/httpd/modules/mod_usertrack.so
LoadModule unique_id_module /opt/jboss/httpd/lib/httpd/modules/mod_unique_id.so
LoadModule setenvif_module /opt/jboss/httpd/lib/httpd/modules/mod_setenvif.so
LoadModule version_module /opt/jboss/httpd/lib/httpd/modules/mod_version.so
LoadModule proxy_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy.so
LoadModule proxy_connect_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy_connect.so
LoadModule proxy_ftp_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy_ftp.so
LoadModule proxy_http_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy_http.so
LoadModule proxy_scgi_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy_scgi.so
LoadModule proxy_ajp_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy_ajp.so
LoadModule proxy_cluster_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy_cluster.so
LoadModule ssl_module /opt/jboss/httpd/lib/httpd/modules/mod_ssl.so
LoadModule mime_module /opt/jboss/httpd/lib/httpd/modules/mod_mime.so
LoadModule dav_module /opt/jboss/httpd/lib/httpd/modules/mod_dav.so
LoadModule status_module /opt/jboss/httpd/lib/httpd/modules/mod_status.so
LoadModule autoindex_module /opt/jboss/httpd/lib/httpd/modules/mod_autoindex.so
LoadModule asis_module /opt/jboss/httpd/lib/httpd/modules/mod_asis.so
LoadModule info_module /opt/jboss/httpd/lib/httpd/modules/mod_info.so
LoadModule suexec_module /opt/jboss/httpd/lib/httpd/modules/mod_suexec.so
LoadModule cgi_module /opt/jboss/httpd/lib/httpd/modules/mod_cgi.so
LoadModule cgid_module /opt/jboss/httpd/lib/httpd/modules/mod_cgid.so
LoadModule jk_module /opt/jboss/httpd/lib/httpd/modules/mod_jk.so
LoadModule manager_module /opt/jboss/httpd/lib/httpd/modules/mod_manager.so
LoadModule slotmem_module /opt/jboss/httpd/lib/httpd/modules/mod_slotmem.so
LoadModule dav_fs_module /opt/jboss/httpd/lib/httpd/modules/mod_dav_fs.so
LoadModule vhost_alias_module /opt/jboss/httpd/lib/httpd/modules/mod_vhost_alias.so
LoadModule negotiation_module /opt/jboss/httpd/lib/httpd/modules/mod_negotiation.so
LoadModule dir_module /opt/jboss/httpd/lib/httpd/modules/mod_dir.so
LoadModule imagemap_module /opt/jboss/httpd/lib/httpd/modules/mod_imagemap.so
LoadModule actions_module /opt/jboss/httpd/lib/httpd/modules/mod_actions.so
LoadModule speling_module /opt/jboss/httpd/lib/httpd/modules/mod_speling.so
LoadModule userdir_module /opt/jboss/httpd/lib/httpd/modules/mod_userdir.so
LoadModule alias_module /opt/jboss/httpd/lib/httpd/modules/mod_alias.so
LoadModule rewrite_module /opt/jboss/httpd/lib/httpd/modules/mod_rewrite.so
<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User daemon
Group daemon
</IfModule>
</IfModule>
# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#
#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin you@example.com
#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
ServerName 10.207.238.66:80
#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/opt/jboss/httpd/htdocs/htdocs"
#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
</Directory>
#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#
#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/opt/jboss/httpd/htdocs/htdocs">
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
#   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important.  Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options # for more information.
#
Options Indexes FollowSymLinks
#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
#   Options FileInfo AuthConfig Limit
#
AllowOverride None
#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all
</Directory>
#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
DirectoryIndex index.html
</IfModule>
#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
Order allow,deny
Deny from all
Satisfy All
</FilesMatch>
#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "logs/error_log"
#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn
<IfModule log_config_module>
#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
<IfModule logio_module>
# You need to enable mod_logio.c to use %I and %O
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
</IfModule>
#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here.  Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
CustomLog "logs/access_log" common
#
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
#CustomLog "logs/access_log" combined
</IfModule>
<IfModule alias_module>
#
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar #
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
#
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL.  You will also likely
# need to provide a <Directory> section to allow access to
# the filesystem path.
#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client.  The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
#
ScriptAlias /cgi-bin/ "/opt/jboss/httpd/htdocs/cgi-bin/"
</IfModule>
<IfModule cgid_module>
#
# ScriptSock: On threaded servers, designate the path to the UNIX
# socket used to communicate with the CGI daemon of mod_cgid.
#
#Scriptsock logs/cgisock
</IfModule>
#
# "/opt/jboss/httpd/htdocs/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/opt/jboss/httpd/htdocs/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain
<IfModule mime_module>
#
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
#
TypesConfig conf/mime.types
#
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#
#AddType application/x-gzip .tgz
#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
#
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz
#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
#AddHandler cgi-script .cgi
# For type maps (negotiated resources):
#AddHandler type-map var
#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml
</IfModule>
#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic
#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html #
#
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or 0 for unlimited
# Default setting is to accept 200 Ranges
#MaxRanges 0
#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off
# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.
# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf
# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf
# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf
# Language settings
#Include conf/extra/httpd-languages.conf
# User home directories
#Include conf/extra/httpd-userdir.conf
# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf
# Virtual hosts
#Include conf/extra/httpd-vhosts.conf
# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf
# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf
# Various default settings
#Include conf/extra/httpd-default.conf
# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
# MOD_CLUSTER_ADDS
# Adjust to you hostname and subnet.
<IfModule manager_module>
Listen 10.207.238.66:6666
ManagerBalancerName mycluster
<VirtualHost 10.207.238.66:6666>
<Location />
Order deny,allow
#     Deny from all
#     Allow from 127.0.0
Allow from all
</Location>
KeepAliveTimeout 300
MaxKeepAliveRequests 0
#ServerAdvertise on http://@IP@:6666 AdvertiseFrequency 5
#AdvertiseSecurityKey secret
#AdvertiseGroup @ADVIP@:23364
EnableMCPMReceive
<Location /mod_cluster_manager>
SetHandler mod_cluster-manager
Order deny,allow
#       Deny from all
#       Allow from 127.0.0
Allow from all
</Location>
</VirtualHost>
</IfModule>

e,启动apache服务

[root@hnxz-vm-mysql-p01 httpd]# ./sbin/apachectl -k start

顺利的话，浏览http://10.207.238.66:6666/mod_cluster_manager 应该能看到类似以下界面：



至此集群已经可以顺利运行，可以访问以前建立的测试项目helloworld

http://10.207.238.66/helloworld/hi.jsp 能顺利访问就可以正常工作，停掉一部分server 继续访问，如果没有问题就证明正常；

具体可参考此文件：
http://www.cnblogs.com/yjmyzz/p/jboss-eap-mod-cluster.html