Thanks dyazbek, yes it works irrespective of whether I add the dependency on barrier or not. but if I add the dependency, there is an error at Jboss starts up, which I guess might be because of some configuration problem, but application is accessible through browser. ok so I decide to ignore this problem, but you have any soln to avoid this ERROR... please provide your inputs. now moving on to the next step... jboss in all the nodes (say 2) was started using "run -c all -b 0.0.0.0" so each instance is bound to the corresponding IP. meaning to say is instance on node 1 is bound to IP1 and instance of node2 is bound to IP2. Now say node 1 is master, the application is accessible on http://<IP1>:8080/<app name>/ not on http://<IP2>:8080/<app name>/ and if node 2 is master, the application is accessible on http://<IP2>:8080/<app name>/ not on http://<IP1>:8080/<app name>/ Problem: As a user of the application, I should not be bothered about what is the master node's IP. there should a domain name or IP for that applicaiton and application should be accessible through that IP or domain name irrespective of which node is Master. So is there any way to configure the IP/domain name, which sheilds user from all this switching from Master to standby and vice-varsa. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176159#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...