Where you lookup a proxy should make no difference as the proxy is cluster aware independent of how its obtained.
Thanks for answering.
Interesting. I had this (wrong) idea that cluster aware stubs would only be available via HA-JNDI and that plain JNDI servers would still have old non-cluster aware stubs.
This raises another problem. In this colocated scenario, it makes no sense to redirect the request to another cluster node. How do I prevent load balancing from happening ?
Look at the org.jboss.invocation.InvokerInterceptor. You can write a customized version to avoid distribution, or write a custom load balancing policy. If you care about where the calls are going, why is the bean clustered?
Ultimately, the bean is clustered to support clustering of an HTTPSession carrying a remote reference to it. Does this make any sense ?
Well, does it make sense or not ? Anyone ?...
Yes, with a stateful session bean that makes sense.