Possibilities include: 1) Don't mark the bean as clustered if you don't want it clustered. The only clustering behavior an SLSB has is failover and loadbalancing; if you don't want that then there is no point making the bean clustered.
2) Only deploy the bean on the server you want, or deploy it in deploy-hasingleton so it's only active on one server. 3) Use FirstAvailable or FirstAvailableIdenticalAllProxies as your load balance policy. These will give varying degrees of server affinity, although the server they initially pick is still random, and each client will independently pick. 4) Some custom load balance policy, perhaps along with a custom interceptor that tells the policy which server to target. The solution depends on what you want; i.e. why load balancing is bad and what server you want the call to go to. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024641#4024641 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024641 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
