-
1. Re: production and development clusters in same network with mod_advertise
pferraro Nov 23, 2010 10:01 AM (in response to th0mas)How did you change the multicast address on your dev nodes?
This should be done via the advertiseGroupAddress & advertisePort properties in the ModClusterConfig bean within mod_cluster-jboss-beans.xml
http://docs.jboss.org/mod_cluster/1.1.0/html/java.properties.html
-
2. Re: production and development clusters in same network with mod_advertise
th0mas Nov 23, 2010 10:25 AM (in response to pferraro)No, I pass this parameter to run.sh with -u option, but it should work, right ?
-
3. Re: production and development clusters in same network with mod_advertise
pferraro Nov 23, 2010 1:33 PM (in response to th0mas)What advertise properties have you defined your mod_cluster-jboss-beans.xml?
If you look at the default mod_cluster AS configuration (from the ModClusterConfig bean):
<!-- Multicast address on which to listen for advertisements -->
<property name="advertiseGroupAddress">${jboss.mod_cluster.advertise.address,jboss.partition.udpGroup:224.0.1.105}</property>
<!-- Port to listen to for advertisements -->
<property name="advertisePort">${jboss.mod_cluster.advertise.port:23364}</property>
<!-- Multicast address on which to listen for advertisements --><property name="advertiseGroupAddress">${jboss.mod_cluster.advertise.address,jboss.partition.udpGroup:224.0.1.105}</property><!-- Port to listen to for advertisements --><property name="advertisePort">${jboss.mod_cluster.advertise.port:23364}</property> -
4. Re: production and development clusters in same network with mod_advertise
th0mas Nov 23, 2010 5:45 PM (in response to pferraro)Yeah, that's the way I have configured my nodes, and httpd have the AdvertiseGroup parameter to only listen multicast address I've configured in dev nodes, so I don't know what else should I configure to make that to work
-
5. Re: production and development clusters in same network with mod_advertise
jfclere Nov 24, 2010 3:25 AM (in response to th0mas)Jose Luis Rodriguez wrote:
Yeah, that's the way I have configured my nodes, and httpd have the AdvertiseGroup parameter to only listen multicast address
the httpd doesn't listen it send the multicast advertise message and the cluster nodes receive it.
What do to have in AdvertiseGroup in production and dev httpd? Does that correspond to advertiseGroupAddress and advertisePort?
you should have something like:
AdvertiseGroup devip:devport which corresponds to advertiseGroupAddress="devip" and advertisePort="devport"
and
AdvertiseGroup prodip:prodport which corresponds to advertiseGroupAddress="prodip" and advertisePort="prodport"
-
6. Re: production and development clusters in same network with mod_advertise
th0mas Nov 24, 2010 10:06 AM (in response to jfclere)In production nodes I have defaults [224.0.1.105:23364], so I don't use AdvertiseGroup directive, in development nodes I do have this directive, something like:
AdvertiseGroup 232.0.0.2:23364
And my problem is in dev nodes
Should I change my port number in dev nodes too ??
-
7. Re: production and development clusters in same network with mod_advertise
jfclere Nov 24, 2010 10:50 AM (in response to th0mas)And my problem is in dev nodes
what do you have in advertiseGroupAddress and advertisePort in those?
Changing the port might help? What platform is it?
-
8. Re: production and development clusters in same network with mod_advertise
th0mas Nov 25, 2010 10:16 AM (in response to jfclere)In configuration files I have the defaults, but when I start it I pass -u parameter to run.sh with address 232.0.0.2. Port is the same
SO is HP-UX, I'll change port and try