Is there any way to not load balance EJB call in WAS cluster?

[Zeke Yang]

Hi,
I have a WAS ND 6.1 cluster containing two nodes. I deploy a stateless session bean in the cluster. I want the two nodes to do things at the same time. I use below way to lookup the EJB on one node:

 
String BEAN_NAME = "cell/nodes/MyHostNode01/servers/node1/oneEJB";
String providerURL = "corbaloc:iiop:MyHost01:2809";
String initialContextFactory = "com.ibm.websphere.naming.WsnInitialContextFactory";

Properties props = new Properties();
props.put(Context.PROVIDER_URL, providerURL);
props.put(Context.INITIAL_CONTEXT_FACTORY, initialContextFactory);

Object obj = ctx.lookup(BEAN_NAME);

You can see that I am using node specific JNDI name, NOT clustered JNDI name like "cell/clusters/MyCluster/oneEJB" to lookup the EJB. I hope using node specific JNDI can lookup the EJB on the given node. But it is not...the lookup is load-banlanced. Sometimes I will get EJB on node 1, sometimes I will get the one on node 2.

Is there any way to let me lookup the EJB on a given node in a cluster? I want both the two nodes to do thing through the EJB at the same time.

And my EJB client is out of cluster now. If I put the client in one of the nodes, I guess all the EJB call will be dispatched to the local EJB in the node, right? I know it is for perfomance consideration. But, is there any way to disable it?

Thank you!