A practical guide to configuring and testing GlassFish 3.1 Clustering
By alexismp on Oct 22, 2010
The main theme for GlassFish 3.1 is clustering which really encompasses centralized admin, load-balancing and in-memory state replication (HA). These features are all available in the 2.x family and are now being introduced in the OSGi-based and JavaEE6-compatible GlassFish product.
While a lot of engineering time has been spent on making the clustering configuration as easy as possible (even with v2.x, see this short demo), one will need to test the configuration and adapt to the networking environment so that's why Shreedhar wrote this recent entry on "How To Configure & Test High Availability with GlassFish Server 3.1 Using A Single Machine"
This blog entry discusses the following :
• the new
asadmin validate-multicast command
• creation of a glassfish cluster with explicit multicast address and port
• use of the
asadmin get-health command to ensure an HA cluster was properly started
• deployment of applications with
--availabilityenabled=true and testing the fail-over
• differences in choosing the replica instances compared to GlassFish v2.x behavior
• how file issues and provide feedback
What may not appear in the list above is the amount of work that went into developing and enhancing the runtime clustering through Shoal's GMS and In-memory replication features (check the one-pagers for more details: In-memory Session Replication, GMS Runtime Clustering, GMS Configuration).
With Milestone 6 scheduled for early next week and the FishCAT program just kicking off (thanks to Richard and other community members!), now is a great time for you to start testing your applications in a GlassFish 3.1 HA environment.