"palin" wrote : | Just an idea for now... this afternoon I was thinking about cluster with Stefano. Did you consider that a real reliable messaging system is most likely going to be deployed on a clustered environment? (I mean, if you're seeking for reliability... why having a single point of failure using a single host?) IMHO it might be a plus to design the RM implementation keeping this cluster-issue in mind. | There's a lot of issues related to the Cluster vs. Web Services. First of all I need to say that clustered environment is the most suitable for stateless web services. It's because if you have stateless services, you do not need to replicate sessions and cluster manager can forward message to any cluster node of his choice. The situation becomes complicated if your web service isn't stateless (and each RM enabled endpoint isn't stateless). Imagine the situation you have RM receivers running on multiple cluster nodes. What you can do in such situation? In real life there is the loadbalancer in the front of cluster and if you have the good one it is cookies aware. Thus the solution for clustered RM environment is: * use cookies aware loadbalancer in the front of cluster * all your RM endpoints (hosted on cluster nodes) must be cookies aware * your cluster must be able to replicate the sessions and cookies * use clustered database (where RM messages are stored) * your cluster can't be hidden behind the filewall If you will meet all these preconditions I don't see the problem to have clustered RM ;-) Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086524#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...