JBoss.org Community Documentation

Chapter 18. Clustered Session EJBs

18.1. Stateless Session Bean in EJB 2.x
18.2. Stateful Session Bean in EJB 2.x
18.2.1. The EJB application configuration
18.2.2. Optimize state replication
18.2.3. The HASessionState service configuration
18.2.4. Handling Cluster Restart
18.2.5. JNDI Lookup Process
18.2.6. SingleRetryInterceptor
18.3. Stateless Session Bean in EJB 3.0
18.4. Stateful Session Beans in EJB 3.0

Session EJBs provide remote invocation services. They are clustered based on the client-side interceptor architecture. The client application for a clustered session bean is exactly the same as the client for the non-clustered version of the session bean, except for a minor change to the java.naming.provier.url system property to enable HA-JNDI lookup (see previous section). No code change or re-compilation is needed on the client side. Now, let's check out how to configure clustered session beans in EJB 2.x and EJB 3.0 server applications respectively.