1 Reply Latest reply on Apr 28, 2007 11:01 PM by Brian Stansberry

    How to configure heartbeat on Cluster env!

    gerald zhou Newbie

      I have 2 nodes on my cluster env with Jboss4.05GA on RedHat AH3.
      Machine1:
      eth0 :192.168.0.173
      eth1: 192.268.100.173
      Maching2:
      eth0: 192.168.0.174
      etho1:192.168.100.174
      "192.168.100.173" and "192.168.100.174" connect directly and the "192.168.0.173" and "192.168.0.174" connecte with a switch. I want the cluster message (UDP message) throws the x.x.100.x. But i also want other server can find this cluster with "jnp:192.168.0.173:1100,jnp:192.168.0.174:1100". How can i configure it. I has try this:
      ./run.sh -c all -b 192.168.100.174 . Then other server cant' find the Jboss server.
      After that, i try again as this:
      ./run.sh -c all -b 192.168.0.174. I find the 2 Jboss server communicate with the x.x.0.x. it's not my wanted.

        • 1. Re: How to configure heartbeat on Cluster env!
          Brian Stansberry Master

          Try:

          ./run.sh -c all -b 192.168.0.174 -Dbind.address=192.168.100.174
          


          JGroups will use the value of the "bind.address" system property to determine what interface to use. Other services use "jboss.bind.address". When you use -b, when JBoss starts it sets both of those properties to the provided value. But if you directly specify "bind.address" as I did above, the value you give will supercede the -b value, so JGroups will use that value.