Outline
We adopt the following five aspects to clear Stateless Session Bean cluster of basic theory:
- No data is lost
- Load Balancing
- Fault Tolerance
- Cluster topology
- EJB client stub
No data is lost
Stateless Session Bean avoids holding data on behalf of its client, which makes Stateless Session Bean cluster becomes simple, because we do not have to worry about losing data.
Load Balancing
EJB Client with a load balancing through the same series of EJB client stub will be transported, i.e., EJB requests handover (sequential calls made by the same client through the same stub can be load balanced across available cluster nodes) on JBoss node.
Fault Tolerance
EJB client stub fault tolerant request to the cluster nodes reachable (fail over a request across the available cluster nodes).
Cluster topology
Cluster topology may be determined by cluster EJB or EJB Client end profile (jboss-ejb-client.properties).
EJB client stub
By JNDI lookup returns a stateless session Bean EJB client stub, which comprises the cluster topology and can successfully load balance or fail over a request across the available cluster nodes. Every EJB transporting cluster information is updated in the stub, which makes the stub in the cluster information is always up to date.
Reproduced in: https: //my.oschina.net/iwuyang/blog/197228