I know about the -b but the system only has one network interface so it's not
an issue.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240871#4240871
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240871
__
Thanks, giddion for the correction and the details. Yep, in my comment format
for the initial_hosts list was incorrect.
Note that if you use -b 0.0.0.0, JGroups will not bind to all interfaces.
Rather it ends up using the value returned by
InetAddress.getLocalHost().getHostName(). You can contr
Ok to update this thread in case anyone else is looking for the same solution.
I followed the post by bstansberry and modified my init script. Ended up with
this run command:
| /opt/jboss/bin/run.sh -c all -b 0.0.0.0 -g cameldev
-Djboss.default.jgroups.stack=tcp
-Djgroups.tcpping.initial_hos
Thank you, this appears to be exactly the information I needed.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240438#4240438
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240438
___
Good question. This topic deserves a wiki page of its own.
Simplest way to solve your problem:
1) Include the following in your command line args that you pass to JBoss:
-Djboss.default.jgroups.stack=tcp
That will change most of the services that use a JGroups channel to use one
based on the "
Digging a little further I've looked through the HANamingService class and it's
dependencies and I don't see properties that I would expect to see if
TCP/unicast/TCPPing were supported.
For example an "InitialHosts" or a "TransportProtocol" is cluster currently
limited to UDP/MCast?
View th
