You'd need to write a custom load balance policy that always picked the first server from the list of targets and then stuck to it. See the code for org.jboss.ha.framework.interfaces.FirstAvailable -- change the part where it using a Random to pick the target.
You'd also have to make sure your active server was completely started before starting the passive. That way the active one would be the first target. This is kind of a quick-and-dirty approach; with thought maybe you can come up with something more elegant. Another point -- if you use the PooledInvoker instead of the JRMPInvoker, the targets the load balancer works on are of type ServerAddress. That class exposes the address of the host it connects to. A custom load balance policy could potentially make use of that info (e.g. check a system property for a "preferred" active host, and access that if its available, otherwise choose a passive host from the remaining targets). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954502#3954502 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954502 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
