C L U S T E R I N G  

    MyEJB 

    MyEJB 

    true 

    MyEntity 

    MyEntity 

    true 

That's it!  You can startup JBoss on different machines and they will automatically figure 

out that they are in a cluster.  All beans flagged as clustered will automatically have fail 

over, load balancing, and replication abilities. 

Cluster wide JNDI 

You can connect to and use the cluster wide JNDI tree simple by leaving the provider URL 

undefined.  JBoss will use IP multicast to discover clustered JNDI. 

jndi.properties 

java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory 

java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces 

Farming 

With JBoss clustering you can hot deploy across the whole cluster just by plopping your 

EAR, WAR, or JAR into the deploy directory of one clustered JBoss instance.  Hot deploying 

on one machine will cause that component to be hot deployed on all instances within the 

cluster. 

Farming is not enabled by default, so you'll have to set it up yourself.  Simply create the 

XML file shown below and copy it to the JBoss deploy directory 

$JBOSS_HOME/server/all/deploy. 

farm service.xml 

41