JBoss Mod_cluster Cluster

1. By deploying the JBoss cluster, we see that it's almost impossible to configure and run, and it's amazing how Mod_cluster found out about JBoss server?

The main is <ifmodule manager_module> node modification, originally some commented out of the configuration

KeepAliveTimeout0#ServerAdvertise on http://127.0.0.1:6666 Advertisefrequency 5224.0.1.105:23364enablemcpmreceive

By reviewing the Mod_cluster documentation,

Serveradvertise: Whether to use the multicast mechanism, the document says the default is off, but I think it should be on

Advertisesecuritykey: Join the cluster key

Advertisegroup: Multicast address, default value 224.0.1.105:23364

Therefore, we can conclude that Mod_cluster broadcast via multicast address 224.0.1.105:23364, notifying JBoss server ' I ' here '

2. Looking at the Domain.xml ha and full-ha configuration, there is a

<subsystem xmlns= "urn:jboss:domain:modcluster:1.1" > <mod-cluster-config advertise-socket= "Modcluster" Connector= "AJP" >   <dynamic-load-provider>      <load-metric type= "busyness"/>      </ Dynamic-load-provider>   </mod-cluster-config></subsystem>

Locate the configuration of the modcluster socket

<socket-binding name= "Modcluster" port= "0" multicast-address= "224.0.1.105" multicast-port= "23364 "/>

Looking back at 1 httpd.conf in the Advertisegroup configuration, the same hey, they are a group, so you can listen to each other through multicast

3. The problem comes, our group of clusters, if in the local area network other people also set up a mod_cluster cluster, as we are the default value, has created a conflict

The workaround is also simple:

Modify Httpd.conf's advertisegroup:224.0.1.106:23364 first,

Then modify the domain.xml of JBoss master and slave to change the ha/full-ha corresponding advertise-socket to: multicast-address= "224.0.1.106" Multicast-port = "23364",

According to the specific situation of their own change, to ensure that both sides are the same IP and port number on the line

In addition: you can see Mod_cluster and JBoss Server to establish a connection using the AJP way, look at the network is configured HTTP compression, it is estimated that the version is not the same, I think in jboss-eap-6.3 as long as modify domain.xml under Ha/full-ha The following node of the profile is changed to HTTP.

<subsystem xmlns= "urn:jboss:domain:modcluster:1.1" >
<mod-cluster-config advertise-socket= "Modcluster" connector= "http" >
<dynamic-load-provider>
<load-metric type= "busyness"/>
</dynamic-load-provider>
</mod-cluster-config>
</subsystem>

This machine simply looked down

Now it's HTTP mode.

Reference:

1. http://blog.csdn.net/kylinsoong/article/details/12292707

2. http://blog.itpub.net/15711267/viewspace-777085/

3. http://www.xcoder.cn/html/web/server/2013/0524/8716.html

4. http://blog.chinaunix.net/uid-26719405-id-4916507.html

JBoss Mod_cluster Cluster