I was not able to reproduce this error myself. The session created after login is successfully replicated to the other node. May I ask the full extent of the changes you made to the booking example to enable clustering? Regarding accessing both servers via a single IP, you'll need another server to act as a load balancer (e.g. Apache HTTP server w/ mod_proxy+mod_cluster, or mod_proxy+mod_proxy_balancer, or mod_jk). The client will access the IP/port of the load balancer which in turn directs the request to one of the servers. More info here: http://httpd.apache.org/docs/2.2/ http://www.jboss.org/mod_cluster http://httpd.apache.org/docs/2.2/mod/mod_proxy.html http://httpd.apache.org/docs/2.2/mod/mod_proxy_balancer.html http://tomcat.apache.org/connectors-doc/index.html Regarding creating redundancy if one node fails, this is achieved through proper replication of all of the stateful elements of your application. You've already enabled session replication, by adding to web.xml. You will also want to replicate any stateful session beans, by adding the @Clustered annotation to the bean classes. If any of your entity beans use hibernate's 2nd-level cache, you'll need to configure hibernate to use a distributed 2nd-level cache, as described here: http://www.jboss.org/community/docs/DOC-13200 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239777#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...