Re: load balancing, if you are trying to call a clustered EJB from inside the app server, there is an optimization that is going to force the call to go to the bean deployed in the local node. See this post for more:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=80210 Re: failover, once you've successfully invoked a method on your bean (on the server), if there is a failure it is going to propagate to your client code, not lead to the client side proxy transparently retrying the call on another server. This is because the proxy has no way of knowing if the call was idempotent; maybe invoking it again will screw up your app. Only your own code can make this decision. Failover will happen if the proxy is unable to make the call on the server. A better test is to do a home lookup, create your SFSB and have your client repeatedly invoke a simple method on it. Have the SFSB log a message every time it's invoked Then while the client is looping and making calls, kill the server it's invoking on. Have your client catch any exception, in case your luck is bad and you kill the server while it's handling a call. You should see the calls fail over to the 2nd node. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3934543#3934543 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3934543 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
