How to configure clustered EJB load balancing policy in EAP 6
Issue
- What is the correct way of changing the EJB load balancing policy? This was using the Clustered interface's loadBalancePolicy attribute in EAP 5.
- What cluster load balancing policy is used for EJB invocations in EAP6 by default
- How the Selector decides when to open a connection with a node in the cluster if already it has not been opened? Does it do it on the basis of load?
- We have a >20 node cluster and a high amount of requests per second, would it be necessary for us to override the default implementation and have a different implementation used?
- As of now, the cluster node selector is set to "org.jboss.ejb.client.RandomClusterNodeSelector", how can I make it do a round robin node selector.
- What EJB load balancing policies are available in EAP 6?
- Is the random load balancing policy the only implementation? What happened to RoundRobin?
- Each EJB invocation will stay local if the requested EJB is locally deployed, can I change that behaviour?
Environment
- JBoss Enterprise Application Platform (EAP)
- 6.x
- 7.0.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.