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
What you have should be fine, except I would change -Dmcast.port=5001 to
-Djboss.hapartition.mcast_port=5001. The different config files that cause
creation of a JGroups channel all specify a system property that you can set;
basically doing what you already did with 'mcast.port' but applying
Bump for some attention :P
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4023606#4023606
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4023606
___
jboss-user mailing list
In regards to setting the mutlicast port as a variable, do I need to set a
variable for both the cluster-service.xml as well as the tomcat cluster config?
Or can I get away with just changing the port for jgoups??
View the original post :
Brian, Thanks allot setting the port to a variable, and adding the bind.address
in the start script seems to have done the trick.
Now all I have left to do is create a script to do this all for us :) loads of
fun.
Larry
View the original post :
Glad it worked. :-)
I'm curious: why 50 partitions?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4020598#4020598
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4020598
___
We have somewhere from 70-80 apps, and we need them to all (well not all but
most) be separate, something to do with SAS70 compliance.
My boss came up with the idea of using a separate instance per application,
except for some small apps / websites.
I don't exactly agree, but they are willing
Missed your question about the tomcat cluster. Yes, you should use a separate
variable for that :(. With JBoss 5, this will be easier as by default all
services will share a single JGroups channel. And there will be a startup
switch (a la -u, -b, etc.) for setting the mcast_port for the
we are using 4.0.5 I have done some testing with 4.0.4 in the past, and did see
when not using different multicast addresses and ports that I get chatter in
the logs from other clusters.
We are using the most recent jdk so I don't think the we will run into the
Promiscuous Traffic issue.
Brian, thanks for all of your help. I do have another question regarding on how
we are setting up the 3 nodes.
I am using apache with mod_jk and want to setup the cluster as follows.
| Node1Node2Node3
| Active Standby Active
| Buddy node2 Buddy
Is 172.25.1.52 associated with bondl? If not, start JBoss like this:
su -l jboss -c '/apps/jboss/bin/run.sh -c foo.bar.com -b 172.25.1.52
-Dbind.address=w.x.y.z -Djboss.partition.name=foo.bar.com --udp=224.10.10.10
/dev/null 2 /dev/null '
where w.x.y.z is an IP address associated with bond1.
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
12 matches
Mail list logo
