JBossDeveloper

Brian, hope you see this.

I am looking at upgrading to 4.2 and am curious as to what the new flags will be....

I notice that the xml files are different now.

Here is what I am curently using to start each instance.

su -l jboss -c '/apps/jboss/bin/run.sh -c D-foo.bar.com -b 10.20.2.193 -g D-foo.bar.com -Dbind.address=172.25.2.101 -u 224.10.10.11 -Dmcast.port=5001 > /dev/null 2> /dev/null &

"bstansberry@jboss.com" wrote:
If the IP passed to -b is not the one you want JGroups to use, specifying it in cluster-service.xml will not work unless you are using JGroups 2.2.8 or later and you pass a special 'ignore.bind.address' system property to java. So, you have two choices:

1) Use JGroups 2.2.8 or later (which is a good idea anyway), and

a) in cluster-service.xml

<UDP bind_addr="172.25.2.14" mcast_addr="${jboss.partition.udpGroup:228.1.2.3}" mcast_port="45566" ...... />

b) to start JBoss:

su -l jboss -c '/apps/jboss/bin/run.sh -c foo.bar.com -b 172.25.1.52 -Dignore.bind.address=true -g foo.bar.com -u 224.10.10.10 > /dev/null 2> /dev/null &'

OR

2) With any JGroups version:

su -l jboss -c '/apps/jboss/bin/run.sh -c foo.bar.com -b 172.25.1.52 -Dbind.address=172.25.2.14 -g foo.bar.com -u 224.10.10.10 > /dev/null 2> /dev/null &'

No need to set the bind_addr in cluster-service.xml with option 2.


IMO, option 2 is easier.

Re: running 50 separate instances per machine, all on separate partitions, you can do that and you can use the same -b and -Dbind.address values for all 50. But you must use separate values for:

1) -g (aka -Djboss.partition.name)
2) -u
3) the value for mcast_port in cluster-service.xml's UDP. Recommend you create a system property for this value and pass it in your startup command via -D.