If we want to make a few JBoss application servers for each other (session only), when a JBoss server in the group down, the user will not be affected, continue to work as a login user, we need to configure clustering, and start the relevant services, That is, the JBoss cluster configuration describes the related JBoss configuration entries:
1), modify the application of the app Web.xml:
Jboss3.2.6:
.. /default/deploy/jbossweb-tomcat50.sar/test.war/web-inf/web.xml
Jboss3.2.3:
. /default/deploy/jbossweb-tomcat41.sar/test.war/web-inf/web.xml
The amendment reads as follows:
< XML version= "1.0"? >
<! DOCTYPE Web-app public
"-//sun Microsystems, INC.//DTD Web application 2.3//en"
"Http://java.sun.com/dtd/web -app_2_3.dtd ">
< web-app >
..... ..... .....
< distributable/>
</web-app >
2), need to start a service cluster-service.xml
If you start the JBoss service with run-c all, the default is to start the Cluster service without having to do any configuration work, just to confirm that the relevant file exists.
Confirm the existence of cluster-service.xml documents under/server/all/deploy/;
Confirm Jgroups.jar file exists under/server/all/lib/, and reinstall JBoss if not.
If the application is deployed under the default configuration, the above two files need to be copied separately
.../server/default/deploy/、.../server/default/lib/directory.
This completes the JBoss cluster configuration, and you can view the log if an exception occurs.