anonymous wrote : | anonymous wrote : | | Hmm, ability to call a single member other than coord seemed like such an obviously good thing that I had to double check to confirm it wasn't already there! :) | | Shouldn't the param be a ClusterNode, which is the type returned by getClusterNodes()? | | | Shouldn't the param be a ClusterNode, which is the type returned by getClusterNodes()? Definitely, good point! anonymous wrote : | anonymous wrote : | | 2. A load balancing policy based on FirstAvailable that always favors a same machine choice. | | | This sounds similar to http://jira.jboss.com/jira/browse/JBAS-4455 which Galder Zamarreno is working on. Probably you guys should coordinate. | JBAS-4455 seems a little different but there could be opportunities to combine our approaches. anonymous wrote : | anonymous wrote : | | 3. A load balancing policy that always picks the ha-singleton server (depends on ha-jndi and a server side ha-singleton). | | | OK. How does it work? | A ha-singleton binds its location (ip address + port) to ha-jndi. The load balancing policy does a ha-jndi lookup of the singleton node and does a little magic to determine which server target is the singleton. Perhaps this could be combined with the JBAS-4455 solution, although it might be easier to understand for application developers to have separate solutions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101434#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...