Hi, does anyone know if there is some workaround to break process affinity in websphere application server (network deployment v6.1) so the workload manager can route part of local ejb requests to remote node machine(s) in a cluster?
According to all the documentation we've read about load-balancing in websphere application server, all ejb requests that come from a local ejb client will be processed within the same application server. I understand this is forced for performance reason. But in my case, I need the load-balancing to be able to forward part of the requests to other nodes in the same cluster.
Also, this ejb client has to be running as a cluster singleton in my application.
Thanks for your reply... Maybe I should have described the scenario in more details.
I have a cluster set up in Websphere to include 2 application servers (nodes). A ejb client is running in one of the 2 servers (the same JVM where the application server runs) to submit requests to some ejb deployed in the cluster.
What I want to achieve is the load-balancing across the entire cluster so that some ejb requests will be handled locally in one server and others will be processed in another server. Because of "Process Affinity" in Websphere, all the ejb requests submitted by that client were procssed only in the local application server and weren't distributted to the remote server (JVM) eventhough round-robin has been set.
For my ejb application deployed in Websphere, there's only remote interface defined. And the ejb client always uses JNDI lookup to find the EJB.
The same application works fine in JBoss which allows overriding of ejb invoker interceptor so that local ejb client can choose between local and remote interface for load-balancing. Check the link from JBoss: