1 of 1 people found this helpful
your start commands looks correct.
The first message is not related to the clustering, the second I don't know ATM.
What version of JBoss do you use?
You should see in your logfile a Messages like 'New Member' or 'Number of members', here you see whether the nodes come together.
Also you can check via JMX console the JGroups state.
If it will not work see the wiki http://community.jboss.org/wiki/TestingJBoss to check, it might be a network configuration issue.
I suppose you try to cluster a webapp, in this case there is no automatic loadbalancing, like for EJB calls, you have to have a balancer in front of JBoss, e.g. Apache.
Nothing appears in either log file about "New Members".
Were using JBossAS 6.0.Final and Windows Server 2008.
Is there a way to confirm the ports that the servers communicate on are open (not disabled by a phantom firewall configuration)?
BTW - there is a load balancer and a Virtual IP. There are no EJBs.
In the TestingJBoss link where it says "If you work with dedicated bind addresses (run.sh -b <ip>) you should start the jgroups test with the additional property '-Djgroups.bind_addr=192.168.128.5', it should be equal to you final JBoss cluster. The bind address will make a difference for the network configuration!"
Would the dedicated bin address be the address of the Virtual IP? Or is that a default Jboss IP address stored in a configuration file?
-Djgroups.bind_addr should be the ip address that you set by run.sh -b XXX
The mcast_addr within the XML config should be the same as you use as the run.sh -u XXX, the default shoulf be 220.127.116.11, see server/all/deploy/cluster/channelfactory.sar/META-INF/jgroups-channelfactory-stacks.xml
In this case the test use the same network routes as the jboss installation.