1. If you're running copies of the "all" configuration on the same network, the copies will be clustered (along with "all" if you're using it). The software and configuration files included in the "all" configuration are cluster enabled by default. You don't need to do anything to "enable" the cluster.
2. To test session load balancing, open sessions on the Apache url. One simple test is to just access the JBoss JMX Console from a new browser session. If you've configured mod_jk for round robin balancing, the console should alternate from one node to the other. 3. In general, the service should work. If you deploy an ear to the farm directory in node1, it should be copied to the farm directory in node 2. However there are some unresolved problems with farming so it may not be working in your situation. 4. You shouldn't need to change the multicast address and port for your JBoss clusters. If you do change them, you need to make the same changes on all nodes in the cluster. Note that the JBoss "all" configuration provides two distinct cluster configurations - one is defined in cluster-service.xml and provides core clustering services. The other is defined in tc5-cluster-service.xml and provides session replication. These clusters are independent and require separate multicast addresses and ports. Jerry View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3907837#3907837 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3907837 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
