I think you have a conceptual misunderstanding here.
- Clustering is done for fault tolerance (aka high availability) of an
application.
- Load balancing is to distribute load, and hence for scalability.
Clustering any object (incl. HTTPSession, Stateful EJB ...) comes at a price,
because the
If your EJB tier consists of SLSBs that are only invoked from the web tier,
don't make them clustered, and don't use HA-JNDI to look them up from the web
tier. JBoss is going to detect that the EJB is available in the same VM as the
web tier and is going to send any call to the EJB in the same
First, client-side interceptors are basically not relevant to an HTTP client
talking to the cluster (e.g. a normal webapp where the client is a browser).
Cluster-aware client side interceptors are involved when a Java client contacts
a server in the cluster and downloads proxy, which it then
Thanks Brian,
I have a situation where the entire application is bundled within a single ear
(the web and the ejb layer are part of the single ear) and deployed in Jboss.
Now since the no. of users has increased and due to performance issues, we have
put 3 instances of jboss machines running
