Mod cluster JBoss Configuration: Difference between revisions
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
/subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=sticky-session,value=true) | /subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=sticky-session,value=true) | ||
</pre> | </pre> | ||
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|mod_cluster Concepts - Sticky Session]]. | For more details on sticky session from a mod_cluster perspective, see [[Mod_cluster_Concepts#Sticky_Session|mod_cluster Concepts - Sticky Session]]. | ||
Revision as of 16:07, 28 June 2016
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
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