-
1. Re: Understanding mod_cluster's discovery process
jfclere Apr 26, 2010 4:04 AM (in response to brettcave)"Does the http side send multicast packets that are received by the java-side multicast listeners?"
Yep that the Advertise mechanism.
httpd sends multicast message that contains the host and port where httpd is wait to receive the nodes information from the cluster nodes,
In case you don't want to use the Advertise stuff you can set the proxyList with the list of httpd servers you run.
(See http://www.jboss.org/mod_cluster/java/properties.html).
-
2. Re: Understanding mod_cluster's discovery process
brettcave Apr 26, 2010 11:54 AM (in response to jfclere)Ok, that makes sense. And the proxyList can be updated via JMX.
I have set up a cluster now, using HAModCluster. My understanding of this is that if any new backend servers were brought onto the same cluster partition, proxy information would be replicated?
This is what I did (using 1.1.0 CR1)
1 x mod_cluster httpd server, no mod_advertise, running manager on ip 192.168.x.y, port 6666
1 x AS 5.1.0.GA server
AS configuration:
jbossweb's server.xml (listener config):
<Listener className="org.jboss.modcluster.catalina.ModClusterListener" advertise="false" />
mod_cluster's jboss-beans.xml:
<bean name="ModClusterListener" mode="On Demand">
<constructor>
<parameter><inject bean="HAModClusterService"/></parameter>
<parameter><inject bean="JMXKernel" property="mbeanServer"/></parameter>
</constructor>
</beanJMX: addProxy 192.168.x.y port 6666
httpd updates with new backendserver.
Start up new AS5 instance, configure with HAModClusterService. Configuration stays empty (it does not find the proxy from AS node1)... should the proxy configuration from node1 replicate to AS node2?