Maybe I can extend the justification a little further: I'd like to have a set-up where I have 2+ nodes, but only one is 'alive-and-kicking' while the others are completely passive. Any clients using the proxy would only interact with the one master server. On a regular fail-over, everything moves over to the next system (currently I have no requirements for a specific fail-over scenario) and the proxy simply starts talking with the new master. Data replication is handled outside of JBoss. Data is NOT time critical. Nothing shall happen if the failed server rejoins. Finally I'd like to be able to trigger such a fail-over. F.i. to force one certain server to become master (again). Environment considerations: * As mentioned, data replication is handled outside of JBoss, as both JBoss AS and DB run on the same nodes. * I have multiple ha-singletons that are needed and can only run once in a productive environment. This is one of the difficulties I had with other designs, as clustering would bring the required actions (start, stop, etc) with it that I would otherwise have to copy. * clients should only interact with the master and be as fail-over tolerant as possible. Also something provided by the clustered proxy, though the 'only-connect-to-the-master' might be a step to take. I have looked into the sources a little bit but have not really found anything yet that indicates if this is even possible. I would really appreciate any help. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4267032#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...