-
1. Re: Cluster setup, using tcp in JBoss AS 6
rnappert Nov 16, 2011 5:18 PM (in response to rnappert)So, when I change my startup to:
run.sh -b 0.0.0.0 -c all -g clusterA -Djgroups.bind_addr=<ip address of local node> -Djboss.default.jgroups.stack=tcp -Djgroups.tcpping.initial_hosts=<ip address of local node>[7600],<ip address of remoote node>[7600]
I don't see this error anymore, but the discovery does not work, which it was working before, because the defaultJGroups conf was used.
Now, I just get:
17:07:51,657 INFO [STDOUT]
17:07:51,657 INFO [STDOUT] ----------------------------------------------------
---------------
17:07:51,657 INFO [STDOUT] GMS: address=<local node>:1099, cluster=clusterA-HAPartition,
physical address=<ip of local node>:55625
17:07:51,657 INFO [STDOUT] ----------------------------------------------------
---------------
17:07:54,694 INFO [JGroupsTransport] Received new cluster view: [<local node>:1099|0] [
<local node>:1099]
although the remote node is running with the cluster-name clusterA.
So, it looks t me that TCPPING is not working.
Any idea?
-Reinhard
-
2. Re: Cluster setup, using tcp in JBoss AS 6
rnappert Nov 17, 2011 10:55 AM (in response to rnappert)I still did not make any progress. The discovery fails in a tcp cluster, using tcpping. I basically used two approaches:
1. Pass system variable with the startup:
-Djgroups.tcpping.initial_hosts=<ip address of local node>[7600],<ip address of remote node>[7600]or
2. Setting initials_hosts attribute in the TCPPING element
initial_hosts="<ip address of local node>[7600],<ip address of remote node>[7600]"
in jgroups-channelfactory-stacks.xml
None of the attempts was successful.
I am sure that someone was able to set a tcp cluster up, using tcpping for discovery. So, any input is highly appreciated.
Thanks
-
3. Re: Cluster setup, using tcp in JBoss AS 6
wdfink Nov 18, 2011 2:55 AM (in response to rnappert)What IP addresses do you use?
Is it the same network?
Is there a firewall or other network stuff in between?
-
4. Re: Cluster setup, using tcp in JBoss AS 6
rnappert Nov 18, 2011 9:09 AM (in response to rnappert)I figured it out!
It had to do with the tcp element in jgroups-channelfactory-stacks.xml. First, I analyzed the WARN messages in server.log, since it was telling me that some TCP aattributes were deprecated. One of them was start_port. There was no mentioing in the clustering guide for 5.1 regarding the deprecation (but I guess this is anyway a jgroups item). Then, I remembered that I have read somewhere that bind_port shouild be used. So after I changed it to :
...
<TCP
singleton_name="tcp"
bind_addr="${jgroups.bind_addr}"
bind_port="${jboss.jgroups.tcp.tcp_port:7600}"
....
it works.
I have to admit that the documentation was not a great help to figure it out ....
Thanks
-
5. Re: Cluster setup, using tcp in JBoss AS 6
rhusar Dec 14, 2011 7:16 PM (in response to rnappert)I figured it out!
Great, you can mark the tread as resolved btw so others know where to look ;-)
-
6. Re: Cluster setup, using tcp in JBoss AS 6
belaban Dec 15, 2011 2:22 AM (in response to rnappert)The documentation is better in 3.x: http://www.jgroups.org/manual-3.x/html/protlist.html#Transport