Mod cluster JBoss Configuration

Overview

EAP 7

<subsystem xmlns="urn:jboss:domain:modcluster:2.0">
    <mod-cluster-config advertise-socket="modcluster" connector="ajp">
        <dynamic-load-provider>
            <load-metric type="cpu"/>
        </dynamic-load-provider>
    </mod-cluster-config>
</subsystem>

Multicast Advertise

Make sure the advertise multicast address and port as the same on the httpd nodes and JBoss nodes. Also make sure multicast propagates between httpd and the JBoss nodes (see #Multicast_Traffic).

TODO: httpd configuration + JBoss configuration

Static Proxy List

<subsystem xmlns="urn:jboss:domain:modcluster:2.0">
    <mod-cluster-config proxies="mod-cluster-proxy-1, mod-cluster-proxy-2" connector="ajp">
        <dynamic-load-provider> ...</dynamic-load-provider>
    </mod-cluster-config>
</subsystem>

...

<socket-binding-group ...>
    <outbound-socket-binding name="mod-cluster-proxy-1">
        <remote-destination host="1.2.3.4" port="6666"/>
    </outbound-socket-binding>
    <outbound-socket-binding name="mod-cluster-proxy-2">
        <remote-destination host="1.2.3.5" port="7777"/>
    </outbound-socket-binding>
</socket-binding-group>

Sticky Session

/subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=sticky-session,value=true)

For JBoss EAP 6.x, sticky session is "on" by default.

For more details on sticky session from a mod_cluster perspective, see mod_cluster Concepts - Sticky Session.

Organizatorium

AdvertiseGroup.

Note that if JBoss AS is used and the -u startup switch is included in the AS startup command, the default AdvertiseGroupAddress is the value passed via the -u