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 uses to invoke operations on servers in the cluster. E.g.: 1) Create an InitialContext configured to use HA-JNDI on port 1100. This results in a communication to the HA-JNDI service on 1100 and the download of a cluster-aware naming service proxy. This is all transparent to your code. When you then do lookups using that context, the proxy includes interceptors that handle load balancing and failover of the naming lookups. 2) Contact JNDI or HA-JNDI (doesn't matter which) and look up an EJB that's configured as clustered. You get an EJB proxy that includes a cluster-aware interceptor. When you make invocations on the bean, the interceptor handles load balancing and failover. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045016#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...