Hi,
Recently , we have tried out ACS in private network and observed with the given scenario and configuration ; duplicate message are send to client .
Scenario: With ACS in private network
Node ips : Node1 = 100.100.10.1
Node2 = 100.100.10.2
Config : Tigase.prop in Node1 : --cluster-nodes= 100.100.10.2
Tigase.prop in Node2 : --cluster-nodes= 100.100.10.1
Login happens successfully with configuration but duplicate message are send to client.
Other Configs that did even connect client (this config works with ACS without private network):
Tigase.prop in Node1 : --cluster-nodes= 100.100.10.2,100.100.10.1
Tigase.prop in Node2 : --cluster-nodes= 100.100.10.2,100.100.10.1
Would be great if you please let us know , does any other config changes required to make it work properly with ACS in private network .
Thanks,
Sourav
For the cluster nodes configuration (either ACS or non-ACS) you must use the hostname:
hostname -f
for the list of cluster nodes. Make sure the hostname has a correct DNS entry to each node can be reached from other nodes by the hostname.
IP address must not be used in configuration.
Hi,
Recently , we have tried out ACS in private network and observed with the given scenario and configuration ; duplicate message are send to client .
Scenario: With ACS in private network
Node ips : Node1 = 100.100.10.1
Config : Tigase.prop in Node1 : --cluster-nodes= 100.100.10.2
Login happens successfully with configuration but duplicate message are send to client.
Other Configs that did even connect client (this config works with ACS without private network):
Tigase.prop in Node1 : --cluster-nodes= 100.100.10.2,100.100.10.1
Tigase.prop in Node2 : --cluster-nodes= 100.100.10.2,100.100.10.1
Would be great if you please let us know , does any other config changes required to make it work properly with ACS in private network .
Thanks,
Sourav